Core Strategy

Testing in an agile project should be not an afterthought but it should be used as an enabler for the project. When including testing and automated testing as part of the sprint deliveries, the team will position itself to keep moving forward instead of having to look back and try to catch up.

This approach does require the following concepts to be implemented:

• "Shift-left" testing
• Test early and often (test relentlessly)
• Automated Static code analysis
• Automated Unit and Integration testing
• Automated functional/business testing
• Full result disclosure

"Shift-left" testing

Shift left testing is an approach to software testing and system testing in which testing is performed earlier in the lifecycle (i.e., moved left on the project timeline). It is the first half of the maxim "Test early and often."

Test early and often

The earlier you test, the earlier you have the opportunity to correct any issues. This cuts down on lengthy feedback cycles and is essential to keep the momentum in an agile project.

Automated Static code analysis

By deploying static code analysis as part of the development/test/build process we keep track of code quality and unit test coverage. Once set up, this is easy, consistent insurance.

Automated Unit and Integration testing

Automated functional/business testing

Full result disclosure