Intro

Agile practices necessitate faster and earlier testing in the software development lifecycle (SDLC). Bringing development and testing together early is commonly referred to as ‘shifting left’.

Traditional testing

A typical, more traditional or waterfall, software development project would organise testing just prior to release into production.
This meant that when bugs were inevitably found, the release would be delayed until these were fixed.
In this model, testing became a bottleneck that seriously impeded the ability of projects to deliver on time.

What’s shift left testing?

The easiest way to explain shift-left software testing is to think of the development cycle as a line running from left to right.
In the old model, testing only came into play on the far right of the line.
To improve quality and recognizing the bottleneck here, we move testing as far to the left as possible, in order to find and prevent defects early in the software delivery process.

Brightest can guide you through this process to make the shift left !

During this session we will show

• Agile quality governance
• How to move towards shift-left (less manual testing)
• Prerequisites
• Roles & responsibilities