Source: thenewstack.io
How We Managed to Test the ‘Untestable’
Deploying an untested change to production will always cause some amount of stress. Every past incident you had when you deployed a change also affects your stress level.
The only requirement for a change to get deployed to production was an approved pull request by one of the engineers.
At first, we thought that testing HAProxy configurations before production was inherent to the type of configuration and the way we use it.
Things that we test are: Access lists and request routing HTTP response status codes HTTP request header injections HTTP response header injections HTTP header or URL path rewrites
The only requirement for a change to get deployed to production was an approved pull request by one of the engineers.
At first, we thought that testing HAProxy configurations before production was inherent to the type of configuration and the way we use it.
Things that we test are: Access lists and request routing HTTP response status codes HTTP request header injections HTTP response header injections HTTP header or URL path rewrites
Related Articles
Community Partners
DevOps Careers