Modern Pipeline - Acceptance Stage
Are your QA Engineers discovering Regression Bugs? They shouldn't have to. You should run automated System Level Tests on your Pipeline, to have assurance that your System works.
📅 Join me for the live workshop ATDD in Legacy Code Roadmap on Wed 6th Aug (17:00 - 19:00 CEST) (100% discount for Optivem Journal members)
🔒 Welcome to the premium Optivem Journal. I’ll help you apply TDD to escape the nightmare of Legacy Code. Join our paid community of 160+ senior engineers & leaders for support on your TDD journey, plus instant access to group chat and live Q&As:
It’s not enough for Components to work in isolation. We need assurance that the whole System works together. In the previous article, Modern Pipeline - Commit Stage, we showed how we can be sure that our Components work in isolation (through Component Level Tests & Unit Level Tests). Now it’s time to find out how we can be sure that the whole System (all the Components working together) works correctly, i.e., are the business requirements satisfied?
Acceptance Stage - Health Checks & Smoke Tests
At the simplest level, we need to automatically deploy the System & run automated Health Checks & Smoke Tests. This tells us that the System is up-and-running:
Note: Within the “Release System“ step, we need to “Configure Environment“. As part of that configuration, we need to configure the connection strings to External Systems to point to External System Test Instances.