Make sure all test classes have one or more consistent group annotations #305
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.
The
@group
annotation allows for the running of groups of tests based on a command line/xml property being set.As the test suite is quite large, this allows for quicker/easier testing of a select group of changed tests/sniffs.
This PR covers:
@group
annotation mirroring the name of the sniff being tested.InternalInterfaces
andNewInterfaces
, both have their own group as well as a secondaryinterfaces
group.utility
+ the name of the function.@group
annotations for single tests in sniff test files as having the annotation for the class will assign it to all tests in that class and that's how it was currently used anyway.