Lines Matching refs:and

4 explain how atest is structured and where the major pieces live and what they
9 2. [Major Files and Dirs](#major-files-and-dirs)
16 Atest is primarily composed of 2 components: [test finders](#test-finders) and
18 1. Parse args and verify environment
23 Let's walk through an example run and highlight what happens under the covers.
27 Atest will first check the environment is setup and then load up the
28 module-info.json file (and build it if it's not detected or we want to rebuild
30 list of all modules in the android repo and some relevant info (e.g.
32 process. We create the results dir for our test runners to dump results in and
37 required and optional bits used to run the test as how the user intended.
38 Required info would be the test name, test dependencies, and the test runner
39 used to run the test. Optional bits would be additional args for the test and
53 ## <a name="major-files-and-dirs">Major Files and Dirs</a>
55 Here is a list of major files and dirs that are important to point out:
60   determines which test finder methods to use and returns them for
65 * ```test_runner_handler.py``` - Module that collects all test runners and
79 runner can understand, and specifying the test runner.
81 For more details and instructions on how to create new test finders,
87 and execute the test as specified.
89 For more details and instructions on how to create new test runners, [go here](./develop_test_runne…