Unit Testing Best Practices
•
3 likes•345 views
This document discusses best practices for unit testing code. It recommends writing tests that are fast, test one thing at a time in isolation, and follow an Arrange-Act-Assert structure. The document also introduces Mockito, a Java testing framework that allows mocking and verifying interactions to further isolate tests. Unit tests provide benefits like ensuring correctness, reducing bugs from changes, better design, documentation, and less debugging time.
Recommended
More Related Content
Similar to Unit Testing Best Practices
Similar to Unit Testing Best Practices (20)
More from Artem Tabalin
Recently uploaded
Recently uploaded (20)
Unit Testing Best Practices
- 1. Unit Testing! How to write better unit tests! ARTEM TABALIN!
- 2. Tests Classification! Unit Tests! Integration Tests! Functional Tests (e2e)! ! A B C A B C A B C D
- 3. Why Unit Testing?! • Assurance of correctness! • Eliminates risk of changes! • Ensures better design! • Provides documentation! • Reduce debug time! • Makes to write loosely coupled code! • Gives confidence!
- 4. Unit Tests Best Practices! Fast as possible! Test first! Arrange → Act → Assert! Assert first! Tests isolation! Test doubles!
- 5. Arrange → Act → Assert!
- 8. Test Doubles! ! ! ! ! • Isolate testing component! • Test integration (not only state)! ! Dummy Stub SpyMock Fake
- 14. Mockito Limitations! • Final classes & methods! • Static methods! • Private methods! • Enums! • Primitive types! • Anonymous classes! !
- 15. Thank you!!