Formatters: allow steps.usage to select what to print #1090
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
For testing of behave repository itself, it'd be useful to have formatters that would report just faulty steps. The steps.usage formatter now read 'steps.usage.classes' user config key and if it's content is comma-separated list of (used|unused|undefined). If it is not recognized this way, all the step classes are printed to maintain the present behaviour for user who could already depend on this very key. Example usage: $ behave --dry -f steps.usage -D steps.usage.classes=unused,undefined
jenisys
force-pushed
the
main
branch
4 times, most recently
from
fe1ca4d
to
fcfe5af
Compare
jenisys
force-pushed
the
main
branch
2 times, most recently
from
0a4d73b
to
2c11d2e
Compare
jenisys
force-pushed
the
main
branch
2 times, most recently
from
3e51dda
to
c6ab01c
Compare
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.
For testing of behave repository itself, it'd be useful to have formatters that would report just faulty steps. The steps.usage formatter now read 'steps.usage.classes' user config key and if it's content is comma-separated list of (used|unused|undefined). If it is not recognized this way, all the step classes are printed to maintain the present behaviour for user who could already depend on this very key.
Example usage:
$ behave --dry -f steps.usage -D steps.usage.classes=unused,undefined