Lines Matching refs:in

3 There are two suites of tests in the Android Runtime (ART):
5   in Java).
11 written in Java and/or [Smali](https://github.com/JesusFreke/smali)
19 The run-tests are identified by directories in this `test` directory, named with
21 sources are in the `src` subdirectory. Sources found in the `src2` directory are
23 exercise "API mismatch" situations by replacing class files created in the first
25 class loaders.  Resources can be stored in the `res` directory, which is
28 The run-tests logic lives in the `test/run-test` Bash script. The execution of a
31 scripts located in the `test/etc` directory (`default-build`, `default-run`, and
38 is actually implemented in the "JAR runner" (`test/etc/run-test-jar`), invoked
42 (implemented in `test/etc/default-check`) is to respectively compare its
44 `expected-stdout.txt` and `expected-stderr.txt` files contained in the test's
47 The `test/run-test` script handles the execution of a single run-test in a given
49 script handling the construction and execution of multiple tests in one
67 Checker assertions are annotations in a run-test's (Java and Smali) source files
72 control-flow graphs (CFGs) for compiled methods at each step (pass) in the
77 ART gtests are written in C++ using the [Google
79 various aspects of the runtime (the logic in `libart`, `libart-compiler`, etc.)
81 as unit tests to verify a particular construct in ART. These tests may depend on
84 ART gtests are defined in various directories within the ART project (usually in
87 in ART's build system (`Android.bp` and `Android*.mk` files). On host, these
89 recommended approach is to run these tests in a chroot environment (see
90 `README.chroot.md` in this directory).
95 All tests in either suite can be run using the `art/test.py`
100 ART also supports running target (device) tests in a chroot environment (see
101 `README.chroot.md` in this directory). This is currently the recommended way to
223 Add "--no_isolate" to run the tests one by one in single process (disable forking).
225 Prefix by "gdb --args " to run the test in gdb.