Repository navigation
Add abort key to suites - #71
Merged
Merged
Conversation
This allows a user to set a suite or test as "fatal" from a suite. I.e. specify which failing tests should abort the execution. Example of test abort: - case: "cases/foo.sh" abort: true - case: "cases/bar.sh" - case: "cases/baz.sh" In the above example, the execution will abort of the foo.sh test fails. Example of suite abort: - suite: "suites/sanity.yaml" abort: true - suite: "suites/mdns.yaml" - suite: "suites/rip.yaml" In the above example, the execution will abort if ANY test in sanity.yaml failes. This new feature is particularly useful for early sanity checks. If the target is down or there's a network problem, there's likely no point in going on with future tests. The --abort flag for the main 9pm.py harness is still there and it makes all tests and suites "fatal". Signed-off-by: Richard Alpe <richard@bit42.se>
Test basic abort functionality. Signed-off-by: Richard Alpe <richard@bit42.se>
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 abort key to suites
This allows a user to set a suite or test as "fatal" from a suite. I.e.
specify which failing tests should abort the execution.
Example of test abort:
abort: true
In the above example, the execution will abort of the foo.sh test fails.
Example of suite abort:
abort: true
In the above example, the execution will abort if ANY test in
sanity.yaml failes.
This new feature is particularly useful for early sanity checks. If the
target is down or there's a network problem, there's likely no point in
going on with future tests.
The --abort flag for the main 9pm.py harness is still there and it
makes all tests and suites "fatal".