Rename assert skipping functions and add possibility to skip a test completely #161
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.
Changes:
*Skipping
functions have been renamed to*SkippingAsserts
to highlight that they are related to skipping asserts. The old functions are available for backwards compatibility but they print out a warning that they are deprecated.skipTest
is introduced that allows all asserts and fails in a test to be skipped. This function must be called in the very beginning of the test case, and if it is called afterstartSkippingAsserts
or any assert/fail function, it will fail the test case. Furthermore, it will print out a warning that the test is skipped, and all asserts and fails in the test case will be skipped without incrementing the assert counters. It will, however, increment a counter for skipped tests, which will be shown in the generated report (skipped tests=X).The documentation and examples have been updated accordingly.