faft: Better tagging on the SUITE field of FAFT tests
This CL tags FAFT tests according the following rules:
faft: All FAFT tests, including BIOS and EC.
faft_normal: All BIOS tests which runs under normal mode.
faft_dev: All BIOS tests which runs under dev mode.
faft_ec: All EC tests.
faft_update: All firmware/kernel AU tests.
faft_stress: All stress tests.
faft_lv1: Basic BIOS tests which verify basic vboot functions.
faft_lv2: Recovery BIOS tests which need external USB disk.
faft_lv3: Corruption BIOS tests which modify firmware/kernel image.
These tests may corrupt the system if any failure happens.
faft_lv4: Advanced BIOS tests which verify not-so-critical features.
You can select the test suites like:
run_remote_tests.sh suite:faft_lv1
If multiple suites are given, it will run all matched tests, like:
run_remote_tests.sh suite:faft_lv1 suite:faft_lv2
BUG=chromium-os:32859
TEST=run_remote_tests.sh --remote=$DUT suite:faft_normal
run_remote_tests.sh --remote=$DUT suite:faft_dev
run_remote_tests.sh --remote=$DUT suite:faft_ec
run_remote_tests.sh --remote=$DUT suite:faft_update
run_remote_tests.sh --remote=$DUT -a "faft_iterations=10" suite:faft_stress
run_remote_tests.sh --remote=$DUT suite:faft_lv1
run_remote_tests.sh --remote=$DUT suite:faft_lv2
run_remote_tests.sh --remote=$DUT suite:faft_lv3
run_remote_tests.sh --remote=$DUT suite:faft_lv4
Change-Id: I141cb7b5b53184ee91d511c5e4a29fb4d17334d2
Reviewed-on: https://gerrit.chromium.org/gerrit/33068
Commit-Ready: Tom Wai-Hong Tam <waihong@chromium.org>
Reviewed-by: Tom Wai-Hong Tam <waihong@chromium.org>
Tested-by: Tom Wai-Hong Tam <waihong@chromium.org>
diff --git a/server/site_tests/firmware_DevScreenTimeout/control b/server/site_tests/firmware_DevScreenTimeout/control
index c251c78..c28054b 100644
--- a/server/site_tests/firmware_DevScreenTimeout/control
+++ b/server/site_tests/firmware_DevScreenTimeout/control
@@ -6,7 +6,7 @@
NAME = "firmware_DevScreenTimeout"
PURPOSE = "Servo based developer firmware screen timeout test"
CRITERIA = "This test will fail if the timeout period does not match our spec."
-SUITE = "faft"
+SUITE = "faft,faft_dev,faft_lv4"
TIME = "LONG"
TEST_CATEGORY = "Functional"
TEST_CLASS = "firmware"