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.

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

Only one assertion per test #16

Open
frankwis opened this issue Feb 15, 2017 · 0 comments
Open

Only one assertion per test #16

frankwis opened this issue Feb 15, 2017 · 0 comments

Comments

@frankwis
Copy link
Member

frankwis commented Feb 15, 2017

In general there should be only one assertion per test method to avoid hiding further assertion failures after the first failing assertion which effectively may hide the real severity of the problem.

See http://blog.jayfields.com/2007/06/testing-one-assertion-per-test.html

Also reoccurring words in several test methods are a sign that the tests should be grouped together, i.e. with @Enclosed. Since that feature is still experimental let's discuss what we want to do.

(See comments for PR #14 )

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant