Run Configuration
Modification of the run configuration is optional. The run configuration is normally generated by the test suite, depending on the options specified in the other configuration files. Typical test suite users will never need to modify the run configuration.
Advanced users may wish to modify the run configuration so meet advanced needs. For example:
- Limit the number of tests or test variations
- When trying to narrow down the cause of a failure in a particular test, or a particular variation of a test, it can be helpful to eliminate all other tests, so that logs, console output, and packet capture files are specific to the narrowed test environment.
- Add variations to existing tests
- If a situation is encountered in the wild that is not yet covered by the test suite, a custom variation can be added. This can be helpful when dealing with individual device differences or unusual situations.
The default location for the run_config.yaml file is:
Advanced users can use the --gen-rc argument when running the suite to generate and save a run_config.yaml file to a specified location. They can edit that file and then run the test suite with the modified run_config with the --use-rc argument.
Future: Recommendations for advanced users
