The Art of Unit Testing

Transcript

1. The Art of Unit Testing Jessica Cecilia Budianto | Software Engineer - Web Platform
2. Agenda • Definition • Principles • Structure • Preferences • Practice
3. Definition
4. The benefits • Helps to detect potential bug in code • Reflects current code quality • Made sure the code still works properly after refactor / major changes • Documents the features and user flows of our code • Trains our mindset to be a better software developer ◦ How user interacts with our code ◦ How edge cases and error might arise from our logic ◦ Improves attention to detail
5. Principles
6. Fast It shouldn’t take long 🤔
7. Isolated / Independent Not depending on other test cases
8. Repeatable Not relying on e.g: network connection
9. Self Validating A test should immediately acknowledges whether it succeeds
10. Timely A test should be able to be written before development even started
11. Understandable A test should be like telling a story
12. Stucture
13. General Test Structure
14. Preferences
15. Top down vs Bottom up
16. https://kentcdodds.com/blog/write-tests
17. Test Driven Development (TDD)
18. But the downsides… • Too focused on testing and making it passed • Time consuming • Harder for big codebase • Even harder if it’s legacy code • Might write a wrong test or miss the edge cases instead
19. Behavior Driven Development (BDD)
20. Practice
21. Github: https://github.com/jessicacb12/ basic-calculator Vercel: https://basic-calculator-psi.vercel.app/
28. Unit Testing will not just affect your code quality, but also your collaboration with stakeholders