Add no-trace on config, test_set and scenario level #35
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.
Add possibility to define
tracer: off
in run.yml configAdd possibility to define
tracer: off
in config.yml at test_set levelAdd possibility to define
tracer: off
in scenario.yml at scenario.yml levelAdd description into tracing.md docs
Some examples:
Example 1. Disable tracer on certain scenarios. Set
tracer: off
on those scenarios where tracing is not needed.Example 2. Your sipssert consists of multiple test sets. You need to disable tracing in some test set as a whole for all scenarios inside that test set. Set
tracer: off
in config.yml on test set level. Tracer will be disabled for all scenarios inside that test set.Example 3. You need to disable tracing on global level. Set
tracer: off
in run.yml file. Remember, that tracing as a whole will be disabled. No one scenario will be traced even if you forcetracer: on
in scenario.yml due to global tracing disabling priority