Unit testing

A brief summary about the importance of Unit Testing.

It was part of an Unit Testing workshop I presented last February 2019.

Transcript

1. Unit Testing fmgonzalez
2. What’s Unit Testing?
3. What’s Unit Testing? - Less bugs due to changes - Less maintenance time - Easier refactors - Provides confidence
4. What should be covered? - Happy path - Controlled errors
5. What should NOT be covered? - Third party services (never use third party services in tests) - Some robustness checks - Framework itself - PHP itself
6. What is coverage? - It’s only another metric - As all metrics we can set a goal - 80-20 rule - Set an agreement between quality (confidence) and effort (costs) - It’s a gamification tool for developers
7. What is coverage?
8. Pros and Cons - Provides confidence - We need this kind of confidence so we need tests - Get 100% of coverage has a high cost not only in effort, also in maintainability - It’s only a metric, a selfish one.
9. Proposal - As a normal tests definition: - Test requirements - Test controlled errors - Set an approval level of coverage (90%) - Don’t use third party services in your tests. Mock them