Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Use pytest-pspec instead of pytest-progress #46

Open
lugi0 opened this issue Nov 26, 2024 · 1 comment · May be fixed by #47
Open

Use pytest-pspec instead of pytest-progress #46

lugi0 opened this issue Nov 26, 2024 · 1 comment · May be fixed by #47

Comments

@lugi0
Copy link
Collaborator

lugi0 commented Nov 26, 2024

pytest-pspec seems to provide a nicer terminal output that takes into account docstrings compared to the plugin currently in use (pytest-progress).
If there's enough interest we could switch to this plugin by default
@lugi0
Copy link
Collaborator Author

lugi0 commented Nov 26, 2024

Current output:
Screenshot 2024-11-26 at 17 10 29

pytest-pspec output:
Screenshot 2024-11-26 at 17 06 45

@lugi0 lugi0 linked a pull request Nov 26, 2024 that will close this issue
Draft
@lugi0 lugi0 linked a pull request Nov 26, 2024 that will close this issue
Use pytest-pspec instead of pytest-progress #47
Draft
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Use pytest-pspec instead of pytest-progress opendatahub-io/opendatahub-tests
1 participant
@lugi0