Lines Matching refs:to
3 Atest is a command line tool that allows users to build, install and run Android tests locally.
4 This markdown will explain how to use atest on the commandline to run android tests.<br>
7 Importantly, when writing your test's build script file (Android.mk), make sure to include
8 the variable `LOCAL_COMPATIBILITY_SUITE`. A good default to use for it is `device-test`.
10 Curious about how atest works? Want to add a feature but not sure where to begin? [Go here.](./docs…
11 Just want to learn about the overall structure? [Go here.](./docs/atest_structure.md)
25 Before you can run atest, you first have to setup your environment.
34 Run the `$ lunch` command to bring up a "menu" of supported devices. Find the device that matches
42 atest command to your $PATH.
48 **atest \<optional arguments> \<tests to run>**
66 <td>Only for instrumentation tests. Waits for debugger prior to execution.</td></tr>
83 #### \<tests to run>
85 The positional argument **\<tests to run>** should be a reference to one or more
86 of the tests you'd like to run. Multiple tests can be run by separating test
98 …More information on how to reference a test can be found under [Identifying Tests.](#identifying-t…
113 Note: Use **TF Integration Test** to run non-module tests integrated directly
124 class and not the whole module. **Module:Class** is the preferred way to run
149 Examples below are ordered by performance from the fastest to the slowest:
173 inputting the path to their test file or dir as appropriate. A single
174 class can also be run by inputting the path to the class's java file.
177 Example - 2 ways to run the `CtsJankDeviceTestCases` module via path:<br>
201 The **-b**, **-i** and **-t** options allow you to specify which steps you want
202 to run. If none of those options are given, then all steps are run. If any of
215 Atest now has the ability to force a test to skip its cleanup/teardown step.
217 to rerun your test with -t will fail without having the **--disable-teardown**
218 parameter. Use **-d** before -t to skip the test clean up step and test
225 So you can continue to rerun your test with just `atest -t <test>` as many times as you want.
230 It is possible to run only specific methods within a test class. While the whole module will
231 still need to be built, this will greatly speed up the time needed to run the tests. To run only
248 Here are the two preferred ways to run a single method, we're specifying the `testFlagChange` metho…
250 allows atest to find the test much faster:
291 `atest <test> --detect-regression </path/to/baseline> --generate-new-metrics <optional iter>`
295 metrics, and compare those against those provided. Note: the developer needs to
296 revert the device/tests to pre-patch state to generate baseline metrics.
300 `atest <test> --detect-regression </path/to/new> --generate-baseline <optional iter>`
307 `atest --detect-regression </path/to/baseline> </path/to/new>`