Lines Matching refs:test_that
3 `test_that` is the supported mechanism to run autotests against Chrome OS
4 devices at your desk. `test_that` replaces an older script, `run_remote_tests`.
7 - CTRL+C kills `test_that` and all its autoserv children. Orphaned processes
10 test_that always runs from the sysroot location.
12 test_that uses autotest_quickmerge to copy your python changes to the
14 - Tests are generally specified to `test_that` by the NAME field of their
18 In addition to running tests against local device, `test_that` can be used to
28 $ test_that -b ${board} ${host} dummy_Pass
34 $ test_that -b ${board} ${host} dummy_Pass.suspend
40 $ test_that -b ${board} ${host} suite:smoke
48 $ test_that -b ${board} ${host} e:login_.*
55 $ test_that -b ${board} ${host} f:.*control.dummy
60 `test_that` now allows you to run jobs in the test lab. The usage is similar to
72 $ test_that -b lumpy -i lumpy-paladin/R38-6009.0.0-rc4 :lab: dummy_Pass
79 and running the tests. `test_that` will return after the suite finishes running,
86 $ test_that -b lumpy -i ${latest_image} :lab: dummy_Pass dummy_Fail
87 $ test_that -b lumpy -i ${latest_image} :lab: e:login_.*
98 test_that -b peach_pit :lab: suite:pyauto_perf -i 'peach_pit-release/R32-4763.0.0'
120 `test_that` allows you to run jobs against a local Autotest setup or a
127 $ test_that -b lumpy -i lumpy-paladin/R38-6009.0.0-rc4 --web 100.96.51.136 :lab:
