Add loglevel argument to pytest. [convenience feature] #645
Conversation
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
carmenbianca
approved these changes
Jan 17, 2023
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.
While starting to work on reuse-tool I first ran the tests and noticed an overwhelming flood of DEBUG outputs.
This PR is my attempt to improve the user experince of running the tests frequently by allowing for a commandline option
--loglevel <LEVEL>. This does break one test that relies on log output, thus this test is skipped, if the loglevel is too high.Feel free to suggest a place to put some instructions on how to use it (if it isn't self-explanatory), as I wasn't sure where an example call would fit best.