Lines Matching refs:Mode

1 # Atest Bazel Mode
5 what we call Atest Standard Mode in this document.
7 Atest Bazel Mode creates a synthetic Bazel workspace and executes tests using
17 4. [Difference from Atest Standard Mode](#difference-from-atest-standard-mode)
22 Atest Bazel Mode commands take the following form:
44 In Atest Bazel Mode, we construct a synthetic workspace using module-info.json.
69 Atest bazel Mode will create the Bazel workspace on first run, or upon detecting
79 ## <a name="difference-from-atest-standard-mode">Difference from Atest Standard Mode</a>
81 Here is a list of major differences from the Atest Standard Mode:
82 * In Atest Standard Mode, user can view detailed test case result in the
83 terminal, while in Bazel Mode only test target result is showing. For test case
84 detail, user would need to look at test logs. The reason Bazel Mode only shows
90 * In Atest Standard Mode, user can identify tests by module name, class name,
91 file path or package name, while in Bazel Mode, we only support module name
93 * In Atest Standard Mode, test logs are saved under ```/tmp/atest_result```, while in
94 Bazel Mode, test logs are saved under ```$ANDROID_BUILD_TOP/out/atest_bazel_workspace/bazel-testlog…
114 ### 2. Why I got "Too many levels of symbolic links" while reading files in Bazel Mode?
117 not work in Bazel Mode.
119 In Bazel Mode, Bazel creates symbolic links for all the test artifacts in the