[7/7] arm/oeqa: add no-op runtime test

Message ID 20220331183117.22389-7-ross.burton@arm.com
State New
Headers show
Series [1/7] runfvp: propagate the exit code correctly | expand

Commit Message

Ross Burton March 31, 2022, 6:31 p.m. UTC
Machines which don't have working network stacks in a FVP can still run
a useful testimage, because it will validate that the machine will boot
to a login prompt on the console.

However, we can't set TEST_SUITES to "" because testimage assumes that
was a mistake, so add a no-op test case for use in these situations.

Signed-off-by: Ross Burton <ross.burton@arm.com>
---
 meta-arm/lib/oeqa/runtime/cases/noop.py | 12 ++++++++++++
 1 file changed, 12 insertions(+)
 create mode 100644 meta-arm/lib/oeqa/runtime/cases/noop.py

Patch

diff --git a/meta-arm/lib/oeqa/runtime/cases/noop.py b/meta-arm/lib/oeqa/runtime/cases/noop.py
new file mode 100644
index 00000000..b5fba7c5
--- /dev/null
+++ b/meta-arm/lib/oeqa/runtime/cases/noop.py
@@ -0,0 +1,12 @@ 
+# SPDX-License-Identifier: MIT
+
+from oeqa.runtime.case import OERuntimeTestCase
+
+class NoopTest(OERuntimeTestCase):
+    """
+    This is a test case which does nothing.  Useful when you want to use
+    testimage to verify that an image boots, but you don't have networking so
+    none of the existing test cases are suitable.
+    """
+    def test_no_op(self):
+        return