@@ -50,7 +50,7 @@ The tests rely on references which need to be generated upfront using reference
When the reference binaries are named `IVAS_cod_ref(.exe)` and `IVAS_dec_ref(.exe)`, pytest will find and use them.
When the reference binaries are named differently, you need to specify them via the `--ref_encoder_path` and `--ref_decoder_path` options.
The tests will used the binaries `IVAS_cod(.exe)` and `IVAS_dec(.exe)` for testing. Please make sure that the binaries have been built before running the tests.
The tests will use the binaries `IVAS_cod(.exe)` and `IVAS_dec(.exe)` for testing. Please make sure that the binaries have been built before running the tests.
When different test binaries are to be used, they can be specified via the `--dut_encoder_path` and `--dut_decoder_path` options.
(DUT: Device Under Test)
@@ -129,3 +129,42 @@ The custom options are listed as part of the pytest help `pytest -h`.
--keep_files By default, the DUT output files of successful tests are deleted.
Use --keep_files to prevent these deletions.
```
## Helper scripts
To help with running the tests during development, two scripts are available in the `tests` folder:
- prepare_pytests.py
- run_pytests.py
The envisioned development workflow is:
```bash
# 1. create a new git branch and switch to the branch
git checkout -b new_branch
# 2. build the REF binaries (here: example for Linux)
make -j
# 3. use the binaries to generate the references for future tests
# assumption: you want to test your development against the start of the development
tests/prepare_pytests.py
# Note: the script will use the binaries IVAS_cod and IVAS_dec in case IVAS_cod_ref and IVAS_dec_ref are not present
# 3a. (optional) store REF binaries in case you want to re-run the reference generation at a later stage
cp IVAS_cod IVAS_cod_ref
cp IVAS_dec IVAS_dec_ref
# 4. do the development changes
edit ...
# 5. build the DUT binaries (here: example for Linux)