Lines Matching refs:run

4 * _ART run-tests_: Tests of the ART runtime using Dex bytecode (mostly written
8 ## ART run-tests
10 ART run-tests are tests exercising the runtime using Dex bytecode. They are
19 The run-tests are identified by directories in this `test` directory, named with
20 a numeric prefix and containing an `info.txt` file. For most run tests, the
28 The run-tests logic lives in the `test/run-test` Bash script. The execution of a
29 run-test has three main parts: building the test, running the test, and checking
31 scripts located in the `test/etc` directory (`default-build`, `default-run`, and
33 `test/run-test`.
35 The default logic for all of these these steps (build, run, check) is overridden
37 (i.e. `build`, `run`, or `check`). Note that the default logic of the "run" step
38 is actually implemented in the "JAR runner" (`test/etc/run-test-jar`), invoked
39 by `test/etc/default-run`.
41 After the execution of a run-test, the check step's default behavior
46 The `test/run-test` script handles the execution of a single run-test in a given
51 To see the invocation options supported by `run-test` and `testrunner.py`, run
54 art/test/run-test --help
73 gtests can be run by executing `m test-art-host-gtest`. On device, the
74 recommended approach is to run these tests in a chroot environment (see
80 All tests in either suite can be run using the `art/test.py`
81 script. Additionally, run-tests can be run individually. All of the tests can be
82 run on the build host, on a USB-attached device, or using the build host
87 run tests on target (rather than using `art/test.py --target`).
89 To see command flags run:
119 ## Running all run-tests on the build host
125 ## Running all run-tests on the target device
131 ## Running one run-test on the build host
137 ## Running one run-test on the target device
146 Both ART run-tests and gtests are run continuously as part of [ART's continuous
148 other test suites are run continuously on this service: Libcore tests and JDWP