Lines Matching refs:to

3 This document explains the practical steps for contributing code to atest.
16 this division, your first step should be to identify the code
19 referring to it as the "Python Code".
24 Its job is to translate user inputs into (1) build targets and (2)
25 information needed for the test runner to run the test. It then invokes
26 the appropriate test runner code to run the tests. As the tests
28 the user. It uses Test Finder and Test Runner classes to do this work.
30 code you'll want to work on.
41 involves how the test is actually run, you'll need to work with this
56 (path relative to android repo root)
62 should have "_unittests" appended to the name. For example, tests
72 directly execute any individual unittest file. However, you'll need to
73 first add atest to your PYTHONPATH via entering in your terminal:
84 to android repo root).
90 to edit if you need to make changes to the TradeFed code.
98 except with the word "Test" appended to the end. <p>
104 TradeFed itself is used to run the TradeFed unittests so you'll need
105 to build TradeFed first. See the
108 There are so many TradeFed tests that you'll probably want to
110 command to run an individual test file is:<br>
114 Thus, to run all the tests in AtestRunnerTest.java, you'd enter:
129 (path relative to android repo root)
133 You shouldn't need to edit vts10-tradefed code, so there is no
134 need to write vts10 tests. Reach out to the vts team
139 Again, you shouldn't need to change vts10-tradefed code.
146 (path relative to android repo root)
150 You shouldn't need to edit this code, so no need to write tests.
154 Again, you shouldn't need to edit this code, so no need to run test.