A Shift Left approach to software development shortens the testing cycle providing the speed and quality that companies need to be competitive, whether they are delivering a single mobile application or a complex multiplatform enterprise software suite. Shift Left practices involve a transformation for the delivery team. Now the entire delivery team contributes to quality, not just the quality assurance or testing team. Lines between the developer and tester fade as they work together to automate testing and partner with operations to make
deployments fast, reliable and repeatable. As teams become more efficient and effective, more resources and time often become available to spend on innovation.
The ingredients to make Shift Left are real and available: automated testing and deployment tools, service virtualization technology, agile practices, and cloud environments. The main obstacle that remains is the mindset of delivery organizations. These groups must transform themselves. The role of the quality assurance tester must include advanced automation and integration testing skills, and developers must see themselves as responsible for quality by testing integrations earlier and more often.
In a way, the adoption of Shift Left processes is a familiar story: people, process and tools. Advances in tooling and acceptance of agile methods are now in place. What remains is to overcome organizational and cultural challenges.
- An approach growing from agile development
- What is Shift Left?
- Shifting Left is a good defense and a good offense
- Is the notion of Shift Left new?
Test the riskiest elements early and continuously. Providing early, iterative feedback on code quality directly to development teams helps ensure that fewer problems are found late in the lifecycle where they are more expensive to fix.