Lines Matching +refs:run +refs:many +refs:tests

7  * GLES capture has many unimplemented functions.
10  * Mid-execution capture has many unimplemented features.
76 To run a sample replay you can use a template located in
77 [samples/capture_replay](../samples/capture_replay). First run your sample and ensure all capture
86 See [samples/BUILD.gn](../samples/BUILD.gn) for details. Then build and run your replay sample:
95 To run your capture on any platform (Windows, Linux, Android, Mac (untested)), you'll need to
98 Create a folder under `src/tests/restricted_traces` that matches the `ANGLE_CAPTURE_LABEL` you
103 src/tests/restricted_traces$ ls -1 desktop_test/
114 [restricted_traces.json](../src/tests/restricted_traces/restricted_traces.json).
121 Now you should be able to compile and run the perf test including your trace:
176     we've run go as high as ID 6.
184     Until we have samples building for Android, the replay sample must be run on desktop.
185     We will also be plumbing replay files into perf and correctness tests which will run on Android.
222 A job unit is a test batch. Each test has to go through 3 stages: capture run, replay build, and
223 replay run. The test batch batches the replay build stage of multiple tests together, and the
224 replay run stage of multiple tests together.
228 ### Running tests
229 From the command line, navigate to the ANGLE root folder [angle][angle_folder] then run the
232 python3 src/tests/capture_replay_tests.py --gtest_filter=*/ES2_Vulkan --keep-temp-files --batch-cou…
235 * `--gtest_filter` to run only specific tests
237 * `--batch-count` to set the number of tests in a (capture) batch. More tests in a batch means that
238 the tests will finish faster, but also means a lower level of granularity.
242 [capture_replay_test_folder]: ../src/tests/capture_replay_tests/
243 [link_to_python_script]: ../src/tests/capture_replay_tests.py
244 [CaptureTrigger]: ../src/tests/restricted_traces/README.md#trigger-the-capture