Lines Matching refs:to

3 You're here because you'd like to contribute to atest. To start off, we'll
5 do. If you're more interested in how to use atest, go to the [README](../README.md).
28 module-info.json file (and build it if it's not detected or we want to rebuild
32 process. We create the results dir for our test runners to dump results in and
33 proceed to the first juicy part of atest, finding tests.
35 The tests specified by the user are passed into the ```CLITranslator``` to
37 required and optional bits used to run the test as how the user intended.
39 used to run the test. Optional bits would be additional args for the test and
46 The final step is to run the tests which is where the test runners do their job.
49 the ```AtestTradefedTestRunner``` is used to kick off ```hello_world_test```.
51 Read on to learn more about the classes mentioned.
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
61   ```CLITranslator``` to utilize.
66   contains logic to determine what test runner to use for a particular
70 * ```constants_default.py``` - Location of constant defaults. Need to override
76 atest to find tests in the android repo based on the user's input (path,
81 For more details and instructions on how to create new test finders,
89 For more details and instructions on how to create new test runners, [go here](./develop_test_runne…
93 You'd like to override some constants but not sure how?  Override them with your
96 1. Create new ```constants_override.py``` (or whatever you'd like to name it) in
98   specify the path to be ```<private repo>/path/to/constants_override/constants_override.py```.
99 2. Add a ```vendorsetup.sh``` script in ```//vendor/<somewhere>``` to export the
103 _path_to_constants_override="$(gettop)/path/to/constants_override"
115 4. You're done! To pick up the override, rerun build/envsetup.sh to kick off the