Allow an alternate top-level test-config.yaml file to be used. #84
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
A new `--testsuite-config=<yaml_file>` option has been added to runtests.py that allows different test configurations to be used without having to swap out the checked-in default `test-config.yaml`. It can be used in the following scenarios: * Realtime tests: The realtime tests require database connection information be specified in the top-level test-config.yaml. Instead of replacing it with a modified version, you can now create a separate file, say `test-config-realtime.yaml` and specify it with `./runtests.py --testsuite-config=./test-config-realtime.yaml ...` * Using a running asterisk instance: Sometimes it's handy to run a testsuite test against a running instance of asterisk. This requires specifying host information in the top-level test-config.yaml. Assuming the instance is properly configured for the test, you can now create a separate file, say `test-config-running.yaml` and specify it with `./runtests.py --testsuite-config=./test-config-running.yaml ...`
|
cherry-pick-to: 18 |
github-actions
bot
added
pr-submit-tests-passed
and removed
pr-submit-testing-in-progress
labels
|
Attention! This pull request may contain issues that could prevent it from being accepted. Please review the checklist below and take the recommended action. If you believe any of these are not applicable, just add a comment and let us know.
Documentation: |
|
Workflow PRCheck completed successfully |
jcolp
approved these changes
Mar 28, 2025
github-actions
bot
added
cherry-pick-testing-in-progress
|
Workflow PRCPCheck completed successfully |
github-actions
bot
added
pre-merge-testing-in-progress
pre-merge-checks-passed
merge-in-progress
and removed
merge-approved
pre-merge-testing-in-progress
labels
|
Successfully merged to branch master and cherry-picked to ["18","20","21","22","certified/18.9","certified/20.7"] |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
A new
--testsuite-config=<yaml_file>option has been added to runtests.pythat allows different test configurations to be used without having to
swap out the checked-in default
test-config.yaml. It can be usedin the following scenarios:
Realtime tests: The realtime tests require database connection information
be specified in the top-level test-config.yaml. Instead of replacing it
with a modified version, you can now create a separate file, say
test-config-realtime.yamland specify it with./runtests.py --testsuite-config=./test-config-realtime.yaml ...Using a running asterisk instance: Sometimes it's handy to run a testsuite
test against a running instance of asterisk. This requires specifying host
information in the top-level test-config.yaml. Assuming the instance is
properly configured for the test, you can now create a separate
file, say
test-config-running.yamland specify it with./runtests.py --testsuite-config=./test-config-running.yaml ...