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

Zero Functionality Release

Start with a zero functionality release. Don’t do any business logic, just get your testing and deployment infrastructure in place.

All programs

Before adding any functionality to your new system get it all the way to production

Setup the continuous integration platform
- For example have a unit test that asserts that one equals one
Write your simplest possible system
- Perhaps make the keep alive endpoint
Set up the deployment code
- For example the code that pushes the artifacts to Artefactory and the systems that push into production
Setup up the performance tests
- For example test the performance of the keep alive end point
Decide how you are going to do Functional Tests
- For example write the functional test for the keep alive endpoint and make sure it passes
Decide how you are going to test your logs
- Write a unit test to check you are producing access logs for the keepalive endpoint

Consider writing a fake pact between the CI platform and your microservice about the behavior of the keep alive endpoint
- You should do this before writing the code for the keep alive endpoint…
- This makes you put in place the pact validation software and the integration with the pact broker
Ask your consumers to write you pacts

Decide how you are going to browser compatability test your component and make sure this happens in the CI pipeline
- If your pipeline doesn’t support this, then make sure you can do it manually on your box