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

22         - [Unit tests](#unit-tests)
23         - [Example tests](#example-tests)
24         - [Encoder tests](#encoder-tests)
25     - [IDE hosted tests](#ide-hosted-tests)
30         - [Running tests directly](#running-test_libaom-directly)
31         - [Running tests via CMake](#running-the-tests-via-the-cmake-build)
55    recommended. A C++ compiler is necessary to build the unit tests and some
82 CMake replaces the configure step typical of many projects. Running CMake will
96 run the generated build will use cc and c++ by default.
100 The AV1 codec library has a great many configuration options. These come in two
106 Both types of options are set at the time CMake is run. The following example
292 3. Build it: run make if that's your generator of choice:
351 #### 1. Unit tests: {#unit-tests}
353 The unit tests can be run at build time:
360     # Note: The AV1 CMake build creates many test targets. Running make
361     # with multiple jobs will speed up the test run significantly.
365 #### 2. Example tests: {#example-tests}
367 The example tests require a bash shell and can be run in the following manner:
373     # It's best to build the testdata target using many make jobs.
380 #### 3. Encoder tests: {#encoder-tests}
382 When making a change to the encoder run encoder tests to confirm that your
384 tests the build configuration should be changed to enable internal encoder
392 The repository contains scripts intended to make running these tests as simple
406 After making your change and creating the baseline clips, you'll need to run
431 ### IDE hosted tests {#ide-hosted-tests}
442     # available, run cmake with the -G argument missing its
494 The AV1 codec library unit tests are built upon gtest which supports sharding of
511 #### 2. Running the tests via the CMake build: {#running-the-tests-via-the-cmake-build}
515     # the IDE hosted tests section above for more information. If the IDE
516     # supports building targets concurrently tests will be sharded by default.
519     # at test run time. This example will run the tests using 10 shards via
524 The maximum number of test targets that can run concurrently is determined by
526 CMake. A system with 24 cores can run 24 test shards using a value of 24 with
622 In addition to the local tests, many more (e.g. asan, tsan, valgrind) will run
678 Sometimes this can’t be done automatically. If you run into this problem, you