New answers tagged

0

Write the smallest simplest tests possible to dry simple DRY SRP code. Mock and Stub external services, most notable the database, so that unit tests run FAST. Accept that good tests can take longer to write than application code. Don't assume all tests remain for regression. prune aggressively once they've driven the code. Make sure there are integrated / ...


2

One remark up-front: You are very aware of the cost of unit-tests. The yield however is sizeable as well. You cannot do without! That being said, I have some ideas for you: What is your goal? Unit-tests should do no more or less than capture you component design. Forget about discovering bugs or detecting regressions. Keep a low profile. Only target a ...



Top 50 recent answers are included