4. Agenda
Some clarifications
5 practical ideas
Answers to your questions
5. Clarification #1: What is a unit test?
A piece of code that checks a unit from
the system under test (SUT)
A unit = a class (basic)
A unit = a behavior (advanced)
8. Clarification #3: When we write tests
Design, Code, Test = Test After
Design, Test, Code = Test First
Programming
Test, Code, Design = Test Driven
Development
9. Clarification #4: Who writes the tests
Technology-facing tests: Devs
Business facing tests: Analysts and Devs
Critique tests: Testers and Devs
10. Clarification #5: Good unit tests
Simple
Fast
Readable
Independent
Repeatable
Easy to run
18. Situation #3
I measure the development time
I want the unit test coverage to be 90%
19. Practical Idea #3
Managers measure Running Tested
Features
Developers measure coverage
Guideline: Coverage must increase
20. Situation #4
We have unit tests, BUT:
We extensively use the debugger
Unit tests are based on test plans
Testers still execute repeatedly manual
test plans
21. Practical Idea #4
Use automated developer tests to:
Executable Specifications
Replace debugging
Complement learning
Replace repetitive manual testing
