Test Driven Development: Difference between revisions
Jump to navigation
Jump to search
| Line 8: | Line 8: | ||
*Acceptable Performance | *Acceptable Performance | ||
=Red Green Refactor= | ==Red Green Refactor== | ||
Start by writing tests with no code, write until test pass, refactor code. This is an iterative approach. | Start by writing tests with no code, write until test pass, refactor code. This is an iterative approach. | ||
[[File:Red green refactor.png| 600px]] | [[File:Red green refactor.png| 600px]] | ||
==Benefits== | |||
*Requirements are verified by the tests | |||
*Regression issues raised early | |||
*Costs of maintenance is lowered | |||
*Design first, when writing the tests first we are designing what they want | |||
*Reduces over engineering | |||
*Easy to know where you are in the project | |||
Revision as of 03:29, 10 December 2020
Introduction
Costs
The cost of software according to this course was
Tests are split into three categories
- Does what was asked for
- Responds appropriately to bad input
- Acceptable Performance
Red Green Refactor
Start by writing tests with no code, write until test pass, refactor code. This is an iterative approach.
Benefits
- Requirements are verified by the tests
- Regression issues raised early
- Costs of maintenance is lowered
- Design first, when writing the tests first we are designing what they want
- Reduces over engineering
- Easy to know where you are in the project