Making automation a default and implicit practice in an agile and DevOps environment helps in ensuring the following:
The existing functionality, if broken by any new code check-in, is called out and reported immediately
The developer is notified and is required to fix it as it happens
The coverage of testing grows as the existing functionality gets validated by automated scripts on daily and nightly builds
The test team can focus on validating new functionality, thus, increasing the velocity of development
While TDD, ATDD, BDD, and service virtualization, all focus on the inside-out view of testing, the test-after approach calls for parallel independent testing that looks at the outside-in aspect of the software.
To ensure that the pace and quality of agile development and testing is maintained in a DevOps implementation framework, refer to the following points:
Automated execution of a minimal set of features in every testable build is advised
The functionality...