Why does JUnit only report the first failure in a single test?
(Submitted by: J. B. Rainsberger) Reporting multiple failures in a single test is generally a sign that the test does too much, compared to what a unit test ought to do. Usually this means either that the test is really a functional/acceptance/customer test or, if it is a unit test, then it is too big a unit test. JUnit is designed to work best with a number of small tests. It executes each test within a separate instance of the test class. It reports failure on each test. Shared setup code is most natural when sharing between tests. This is a design decision that permeates JUnit, and when you decide to report multiple failures per test, you begin to fight against JUnit. This is not recommended. Long tests are a design smell and indicate the likelihood of a design problem. Kent Beck is fond of saying in this case that “there is an opportunity to learn something about your design.
(Submitted by: J. B. Rainsberger) Reporting multiple failures in a single test is generally a sign that the test does too much, compared to what a unit test ought to do. Usually this means either that the test is really a functional/acceptance/customer test or, if it is a unit test, then it is too big a unit test. JUnit is designed to work best with a number of small tests. It executes each test within a separate instance of the test class. It reports failure on each test. Shared setup code is most natural when sharing between tests. This is a design decision that permeates JUnit, and when you decide to report multiple failures per test, you begin to fight against JUnit. This is not recommended. Long tests are a design smell and indicate the likelihood of a design problem. Kent Beck is fond of saying in this case that “there is an opportunity to learn something about your design.” We would like to see a pattern language develop around these problems, but it has not yet been written dow
(Submitted by: J. B. Rainsberger)Reporting multiple failures in a single test is generally a sign that the test does too much, compared to what a unit test ought to do. Usually this means either that the test is really a functional/acceptance/customer test or, if it is a unit test, then it is too big a unit test.JUnit is designed to work best with a number of small tests. It executes each test within a separate instance of the test class. It reports failure on each test. Shared setup code is most natural when sharing between tests. This is a design decision that permeates JUnit, and when you decide to report multiple failures per test, you begin to fight against JUnit. This is not recommended.Long tests are a design smell and indicate the likelihood of a design problem. Kent Beck is fond of saying in this case that “there is an opportunity to learn something about your design.” We would like to see a pattern language develop around these problems, but it has not yet been written down.
