-
Notifications
You must be signed in to change notification settings - Fork 0
docs: 📝 decision post on why to use pytest #102
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.
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
Conversation
martonvago
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍 👍 👍
signekb
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Very nice! I have some suggestions 🚀
why-pytest/index.qmd
Outdated
| all tests need to be a `class` object and some testing needs | ||
| `setUp()` and `tearDown()` methods. | ||
| - The test output is not very readable and beginner friendly. | ||
| - Creating tests takes more effort and time. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
more effort and time as compared to what? :)
Co-authored-by: Signe Kirk Brødbæk <40836345+signekb@users.noreply.github.com> Co-authored-by: martonvago <57952344+martonvago@users.noreply.github.com>
Description
Add decision post on why to switch to pytest.
Closes #101, see also seedcase-project/seedcase-sprout#226
Reviewer Focus
This PR needs a bit of a review.
Checklist