Goal
We will deliver World Class Software
This policy identifies ‘Continuous Delivery’ as the first stage in that transformation. In order to get to continuous delivery, most of us need to improve our working practices. In order to achieve Continuous Delivery our testing policy must deliver:
| Concept | |
|---|---|
| Shift Left | Pushs the testing as early as possible in the development cycle as possible |
| Invert The Pyramid |
Most projects have a test shape that looks like an ice cream cone. We must invert that and make our tests look like the picture below |
| ‘boy scout rule’ | Removes technical debt and delivers clean code |
| Automate testing | As much as is possible to automate should be automated |
Testing Pyramid
Policy
This policy is opinionated. It makes claims that the best code is the code that can be heavily unit tested, and is precise and rigorous on what a unit test is. This is the policy of the company that you work for. If you don’t understand why this policy is like this talk to your colleagues, read the internet or request training. If you don’t know how to write code in line with the policy then don’t stay quiet: request training
- Working practices: how you should undertake your work
- Minumum standards: the least you must do
- Code guidelines: what is the definition of good quality code?
- Test guidelines: how do we write tests?
- Your Duty: you must write quality code and not accept long term technical debt
- What should be tested: Everything that can be automated
- Glossary