Implementing integration test automation to run after the development pipelines ensures defects are found earlier in the lifecycle and regression of primary functionality is always satisfied with incremental code delivery. The specific case study for setting up the infrastructure necessary for running integration test suites as part of the pipeline would be using the following tech stack – Bitbucket for code hosting and collaboration, AWS as the cloud platform, and SmartBear TestComplete as the functional test automation tool.

Once certain standards are laid out, for example, which test environment to perform integration tests on, the continuous execution of a regression/ sanity suite in the pre-production integration environment would greatly increase the confidence in the quality of the outcome. Since the run reports can be set visible to all stakeholders, it promotes transparency in the team.

Bulkier test suites can be run as part of nightly executions and smoke testing suites can be run as part of the pipeline. The infrastructure could also be set up so that the cost of utilization can be easily tracked in the cloud platform and optimized for regular usage. Triggers for execution can be Slack, a scheduled trigger, or a pipeline deployment.

In summary, she will be spending time upfront and setting up the infrastructure once can reap rewards long-term in reducing the release cycle without compromising on quality.


May 5 @ 11:30
11:30 — 12:15 (45′)

Aarti Suresh