Introduction to Test Driven Development [TDD]
2 likes642 views
This document introduces test-driven development (TDD) by outlining its key principles and best practices. It discusses why TDD is used, the three laws of TDD, how to approach TDD professionally, conventions for well-written tests, common tools for TDD, and provides a hands-on example of building a calculator service with TDD. The goal is to help readers understand the TDD philosophy, practice TDD techniques properly, and write use case-driven unit tests.
![TEST DRIVEN
DEVELOPMENT [TDD]
An Introduction
Ashish K
Agarwal
Vijay S Dey](https://image.slidesharecdn.com/tddorientation-130806112917-phpapp01/85/Introduction-to-Test-Driven-Development-TDD-1-320.jpg)
Introduction to Test Driven Development [TDD]
- 1. TEST DRIVEN DEVELOPMENT [TDD] An Introduction Ashish K Agarwal Vijay S Dey
- 2. Takeaways Understand the TDD philosophy Oriented towards TDD practice Aware of techniques for TDD Write use case driven unit tests
- 3. Contents Why TDD Three laws of TDD Professional attitude towards TDD Conventions for well written tests Tools for TDD Common TDD mistakes
- 4. Why TDD? It helps clarify business requirements Allows to identify bug ahead of time Develops the system incrementally Gains confidence in our own code Helps maintain the code
- 5. Three laws of TDD
- 6. Professional attitude towards TDD Think about the tests first Break the problem into smaller units Treat the test code on par with production code Have tests as documentation of the actual code “Be Nice” to fellow developers
- 7. Conventions for well written tests Name of test – should indicate the business intent so when the test fails, dev knows why it matters E.g. testHappyPath() ShouldAlertUserWhenInputIsEmpty()
- 8. Conventions (cont’d) Skeleton of test – Setup -> Execute -> Verify E.g.
- 11. Tools for TDD Junit framework Mockito Test code coverage – e.g. Clover
- 13. Takeaways Understand the TDD philosophy Oriented towards TDD practice Aware of techniques for TDD Write use case driven unit tests