-
Notifications
You must be signed in to change notification settings - Fork 108
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
Add guideline to write tests #185
Conversation
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.
I did a first pass on formatting
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.
Some simple clarity changes for you :) This is almost ready; we can revise this as we go.
Co-authored-by: Alice Cecile <alice.i.cecile@gmail.com>
Yup, those are clearer, thanks! |
* Add test guideline * Space around lists * Fix idents and numbering * Remove double wrapped integration-test example * Add note of paramter-based testing * Apply suggestions from code review Co-authored-by: Alice Cecile <alice.i.cecile@gmail.com> Co-authored-by: Alice Cecile <alice.i.cecile@gmail.com>
Objective
As discussed in #179, this adds a short guideline for how to write and organise tests within
taffy
Context
Mostly to help people such as myself that are unfamiliar with this, but also just to ensure consistency and consensus through the project.
Also, we need a lot of tests to any way we can make it simpler to contribute on the testing side is a win!
Feedback wanted
I don't want it to be too terse or verbose, so please comment on phrasing ++