Automated Tests, Unit tests, Pros (1)
16 Oct 2009 Tags:tdd
My humble opinion only
- Improves design.
At least +1 client, decoupling from the Application.main([]) method.
- Regression tests, cost of running them VS cost of manual retesting.
- Difficult to test by mortal hand areas
(multi-threading issues, timing, DB connectivity loses). As extra point, the cost of such hand-made tests are extremely high and won’t disappear on 2nd/3rd/… run. Not my opinion, but I share this point of view
- Easier to explore internal (unclear from user point's of view) Grey Areas or Unpredictability Corners (more commonly known as old plain Boundary Values).
It’s not always clear from User Story or User Interface that the boundary values would be, or other subsystem boundary values influence on this particular component. Or the boundary value application will eventually hit is very-hard to prepare by mortal hand. For example tester should repeat Long.MAX_VALUE operations to hit this one.
NB. If you've found typos or errors, please suggest a correction or edit on github.