T

test driven development

In test driven development, unit tests are created before the related application’s change. There is a continual cycle of:
1. Create a test that fails,
2. Write code until the new test succeeds, and
3. Repeat.

This approach helps ensure:
– Code is written in a way that supports unit testing, and
– Unit Test Code Coverage (and confidence in our change) is high.


testing

The process by which we confirm that the application performs correctly and efficiently. Testing can be done automatically (by other code) or manually (by a person). However, investment in automated tests helps ensure that we:

  • Maintain a consistent speed for developer productivity as the application continues to grow and change,
  • Have higher confidence in the changes we make to the application in the future (both that they produce the desired output (correct) and perform with the speed and resource efficiency that we expect).

testing pyramid

A visualization to help us understand where our test cases should be focused and a layered strategy that may help the team see the most benefit from automated testing.