This is advice not policy. It is not mandatory, however it is recommended

Check your testing stages

• Do you have Continuous Integration in place?
• Are the Unit tests actually running in the CI pipeline?
• Do you have Pact Consumer Tests in place with your providers (if you have providers)?
• Do you have Pact Verification Tests in place with your consumers (if you have consumers)?
• Do you have Performance Tests in place?
• Is the security checking software in place as part of the CI pipeline?
• Do you have browser compatibility testing in place for your web components?
• Can all the above tests run on your local box, or do they need a special environment?

Fix any issues with the above

Treat this a little like a greenfield site project and make sure that the essential testing structures are in place in your pipeline

Adding functionality

• Make sure you have a functional test for your new functionality
  • This can be a pact test or a functional test.
  • Pact tests are adequate for many systems.
• Make sure that the functional test fails.
  • If it passes you have probably written it wrong
  • Make sure it is in the pipeline (it is acceptable for functional tests to fail: that shouldn’t stop us going live)
• Follow the advice in Working Practices with