TDD (Test-Driven Development) Introduction

- TDD (Test Driven Development)
- Intro
Evoloutionary approach to development which combines: test-first, fulfill the test and refactoring
Require great discipline from programmer
Enables programmer to take small solid steps when writing software
- Kinds of tests
- Unit Tests: Test internal funcionalities with small parts to see if it is working properly
- System: After the development group of users start use system fucionalities to assess the behavior
- Integration: Tests the integration between components
- Sanity: Test to determine if a new software version is performing well enough to accept it for a major test effort
- load: User hearvy loads such as web calls
- Stress: System is stress and perform under heavy load, traffic, large number of storage capacity or database.
- Performance: Verify the performance using both stress and load tests
- Acceptance: End users analises whether the application fits to the requirements
- Philosophy
- Develop and implement unit tests before writing any line of code
- First the test must fail
- Code is developed after test is developed
- Steps
- Add a test
- Run the test(must fail)
- Develop code
- Run the test

- Benefits
- Shortens the programming feedback
- Provides detailed (executable) specifications
- High-quality code
- Concrete evidence that your code works
- Prove the code works with a code
- Support evolutionary development