Information Technology Reference
In-Depth Information
Practice
Description
Limit test cases to
one assert
Spend less time tracking down the cause of a test
failure by limiting your automated tests to one asser-
tion per test.
Use this list of questions to evaluate your test process in light of the CI
environment and what it can provide for you.
■
Are you categorizing your automated tests, such as unit tests, com-
ponent tests, system tests, and functional tests?
■
Are you configuring your CI system to run each test category with
different staged builds?
■
Are you writing automated unit tests for each defect?
■
How many asserts are in each of your test cases? Are you limiting
each test case to one assert?
■
Are these tests automatable? Has your project committed auto-
mated developer tests to the version control repository?
