Backing slides for my internal introductory webinar, "fighting complexity with unit testing and code review". Public version is slightly modified.

1. Fighting complexity
WITH UNIT TESTING AND CODE REVIEW

2. Agenda
1. Accidental complexity
2. Unit testing
3. Code Review

7. Typical effects
• Development productivity
• Maintenance costs
• Defect rate & severity
• Sanity
• Job security

9. Unit (classic)
Mock
Integration

10. Unit testing
Refactoring Spec
Continuous
Integration
Design QA

11. http://martinfowler.com/bliki/TestCoverage.html

13. Code review
- Before commit
- After commit
- Before merge
- After merge

14. Code review
- Code quality
- Completeness
- Test coverage
- (…)
- Simplicity

15. Beware of
• Unnecessary abstractions
• Excessive indirection layers
• Redundant technologies
• Premature optimization
Simplicity

17. So how do I start?
Well, 2 simple steps:

18. So how do I start?
Well, 2 simple steps:
- You stop not testing
- You stop not doing reviews

19. Ok, seriously
CODE REVIEW
* Sell the idea to the team
* Decide on standards
* Don’t spend much time on the tools!
* Hook code review to your development
process
UNIT TESTING
* Sell the idea to the team
* Look at examples, e.g open-source projects
* Add tests for a simple existing component(s)
* Be prepared for refactoring
* Hook JUnit to your build process & CI
* Add coverage validation to the code review

21. Thank you!
Questions? Comments?
http://junit.org/
https://code.google.com/p/mockito/
http://emma.sourceforge.net/
http://vimeo.com/10569751
Pavel_Grushetzky@epam.com
ORGCompetencyJava@epam.com