Use pytest-pspec instead of pytest-progress #47
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
Signed-off-by: lugi0 <lgiorgi@redhat.com>
|
Discuss in #46 |
|
@lugi0 looked into using this plugin. i think we should continue using pytest-progress as it provides visibility on tests progress which is important mainly in ci. i think logging the test docs in this context is less valuable. wdyt? |
|
@rnetser I honestly don't like how verbose pytest-progress is most of the time, but I agree that in CI it would be the better choice. |
|
@lugi0 I prefer not to have 2 configs and as the target here is mainly ci I think we should go with pytest-progress. |
|
@lugi0 can we close this one? |
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.
Implementation of #46