diff options
| author | Daisuke Nojiri <dnojiri@chromium.org> | 2017-04-12 09:48:10 -0700 |
|---|---|---|
| committer | chrome-bot <chrome-bot@chromium.org> | 2017-06-23 00:51:19 -0700 |
| commit | ff85876719777d7e375368f73ec0c150a134f291 (patch) | |
| tree | ac78df3efe0c1d353a95ac0a2c18aca3b08b9168 /cts/meta/cts.testlist | |
| parent | 60800678ca1a7454a20ae2c270a4ea0bda34b9c0 (diff) | |
| download | chrome-ec-ff85876719777d7e375368f73ec0c150a134f291.tar.gz | |
eCTS: Check order and expectation of test results
This patch makes the framework verify not only the result but also
the execution order of the tests. It also allows each test to
specify expected return code and strings printed by TH and DUT.
The final test results depends on the return code and the expectation.
Therefore, the output now includes 'RESULT' column showing PASS or FAIL:
test name TH_RETURN_CODE DUT_RETURN_CODE TH_STR DUT_STR RESULT
test_task_switch SUCCESS SUCCESS 1 1 PASS
test_task_priority SUCCESS FAILURE 1 1 FAIL
test_stack_overflow DID_NOT_END DID_NOT_END 1 1 PASS
Additionally, this patch:
* Adds CTS_RC_DID_NOT_START and CTS_RC_DID_NOT_END to indicate whether
the test did start or end, respectively.
* Makes stack overflow test check whether stack overflow was detected
and reboot occurred
* Removes post_corruption_test and conflict test since now
the test results are stricly compared against expected results.
* Fixes gpylint errors.
BUG=none
BRANCH=none
TEST=Run gpio, meta, timer, interrupt, and cts/cts.py -m task
Change-Id: I3b7005236e705dcac0c8f4711b44c85ff9a4f676
Reviewed-on: https://chromium-review.googlesource.com/538878
Commit-Ready: Daisuke Nojiri <dnojiri@chromium.org>
Tested-by: Daisuke Nojiri <dnojiri@chromium.org>
Reviewed-by: Daisuke Nojiri <dnojiri@chromium.org>
Diffstat (limited to 'cts/meta/cts.testlist')
| -rw-r--r-- | cts/meta/cts.testlist | 28 |
1 files changed, 8 insertions, 20 deletions
diff --git a/cts/meta/cts.testlist b/cts/meta/cts.testlist index 778b0f62cc..d453d33e51 100644 --- a/cts/meta/cts.testlist +++ b/cts/meta/cts.testlist @@ -12,53 +12,41 @@ * 3 * 4 */ -CTS_TEST(debug_test) +CTS_TEST(debug_test,,,,) /* Test should succeed if both report success * (expected result: success) */ -CTS_TEST(success_test) +CTS_TEST(success_test,,,,) /* Test should fail if one reports success and * (one reports failure (expected result: failure) */ -CTS_TEST(fail_dut_test) +CTS_TEST(fail_dut_test,,, CTS_RC_FAILURE,) /* Test should fail if one reports success and * (one reports failure (expected result: failure) */ -CTS_TEST(fail_th_test) +CTS_TEST(fail_th_test, CTS_RC_FAILURE,,,) /* Test should fail when both boards report failure * (expected result: failure) */ -CTS_TEST(fail_both_test) +CTS_TEST(fail_both_test, CTS_RC_FAILURE,, CTS_RC_FAILURE,) /* Test should fail with bad sync if one reports bad * sync and the other reports success (expected result: * bad_sync) */ -CTS_TEST(bad_sync_and_success_test) +CTS_TEST(bad_sync_and_success_test, CTS_RC_BAD_SYNC,,,) /* Test should fail with bad sync if both boards report * bad sync (expected result: bad_sync) */ -CTS_TEST(bad_sync_both_test) - -/* Test should report conflict if one reports bad sync - * and the other reports failure - * (expected result: conflict) - */ -CTS_TEST(bad_sync_failure_test) +CTS_TEST(bad_sync_both_test, CTS_RC_BAD_SYNC,, CTS_RC_BAD_SYNC,) /* Test should be listed as corrupted if one test hangs, * regardless of what the other test outputs * (expected result: corrupted) */ -CTS_TEST(hang_test) - -/* Test should be corrupted if it follows a corrupted - * test, regardless of what the actual result was - * reported as - */ -CTS_TEST(post_corruption_success)
\ No newline at end of file +CTS_TEST(hang_test, CTS_RC_SUCCESS,, CTS_RC_DID_NOT_END,) |