<summary>Example Output of CUT execution</summary>
<pre><code>
```console
Accumulating commands from Readme_IVAS_dec.txt
Accumulating commands from Readme_IVAS_rend.txt
Accumulating commands from Readme_IVAS_enc.txt
Accumulating commands from Readme_IVAS_ISAR_post_rend.txt
Accumulating commands from Readme_IVAS_ISAR_dec.txt
Accumulating commands from Readme_IVAS_JBM_dec.txt
No of tests :
ENC : 381
DEC : 637
REND : 666
ISAR_ENC : 1032
ISAR : 1032
Executing tests for ENC (381 tests)
Executing tests for DEC (637 tests)
Executing tests for REND (666 tests)
Executing tests for ISAR_ENC (1032 tests)
Executing tests for ISAR (1032 tests)
</code></pre>
Executing tests for ENC (381 tests):
---------------------------
[ENC] OK
...
Summary of results:
---------------------
[ENC] OK
[DEC] OK
[REND] OK
[ISAR_ENC] OK
[ISAR] OK
```
</details>
This should generate outputs in scripts/CUT_OUTPUTS folder which looks like below:-
@@ -106,7 +117,7 @@ If CUT test execution is done on a different platform, the scripts/CUT_OUTPUTS m
### Perform the BE comparison on the CUT outputs on reference platform
The BE comparison is performed to the CUT outputs using the command below. Encoded outputs will be decoded using the reference decoder executables as part of the process. The BE comparison is then performed between the CUT and reference decoded outputs. This includes comparison of ".wav"-files, and ".csv" and ".met" metadata files. If any non-BE results are observed, this is reported on the command-line and link to an analysis ".csv" file is given. The analysis file shows which exact files were non-BE. An example passing output is shown below. If all test sets print `PASSED BE TEST`, then CUT outputs are BE-conformant.
The BE comparison is performed to the CUT outputs using the command below. Encoded outputs are decoded using the reference decoder executables as part of the process. The BE comparison is then performed between the CUT and reference decoded outputs. This includes comparison of `.wav`files and `.csv`/`.met` metadata files. If non-BE results are observed, this is reported on the commandline and in the generated analysis CSV output.
MLD Corridor passed for ISAR with max MLD diff of 0.0
</code></pre>
</details>
## Executing specific tests only
All CUT tests can be run specifically for IVAS Encoder,IVAS Decoder,IVAS Renderer, ISAR Encoder and ISAR Decoder only. The commandline allows for ```-test-mode=<PARAM>``` for this functionality, examples:
Use `--filter TOKEN` to select test groups, output formats, and apply substring matching.
- Run CUT IVAS Encoder Tests Only (on Target Platform)
- Token types:
-`ENC`, `DEC`, `REND`, `ISAR`, `ISAR_ENC`: test groups.
-`MC` expands to `5_1`, `7_1`, `5_1_4`, `5_1_2`, `7_1_4`.
- Any other token is treated as a case-insensitive substring match.
- Token modifiers:
-`TOKEN`: restrictive token. Multiple restrictive tokens combine with logical AND.
-`+TOKEN`: additive token. Adds matching tests even if they would otherwise be excluded.
-`-TOKEN`: subtractive token. Removes matching tests from the final selection.
-`TOKEN*`: wildcard token. Matches all known tokens starting with the given prefix.
-`+TOKEN*`, `-TOKEN*`: wildcard token with add/remove behavior.
-**Note**: wildcards must be quoted in shell (e.g. `'ISAR*'`) to prevent the shell from expanding them as filename globs before the script receives them.