TL;DR: Shift-Left is about testing early and automated. Shift technical with this trend or facilitate that testing happens.
Shift-Left is the label we apply when testing moves closer to development and integrated into the development activities. The concept is many IT years old, and there are already some excellent articles out there: What the Shift Left in Testing Means (Smart Bear, no date), “Shift left” has become “drop right” (Test Plant 2014), Shift Left QA. How to do it. Why it matters (Work Soft, 2015).
To me Shift-Left is still an active trend and change how to do testing. This goes along with Shift-Right, Shift-Coach and Shift-Deliver discussed separately. I discussed these trend labels at Nordic Testing Days 2016 during the talk “How to Test in IT operations“.
Here are some contexts where Shift-Left happens:
- Google have “Software Engineer in Test” as job title according to the book “How we Test Software at Google“.
- Microsoft have similar “Software Design Engineer in Test” as discussed by Alan Page in “The SDET Pendulum” and in the e-book “A-word“
- A project I was regarding pharmaceutical Track and Trace, had no testers. I didn’t even test but did compliance documentation of test activities. The developers tested. First via peer review, then via peer execution of story tests and then validation activities. No testers, just the same team – for various reasons.
- A project I was in regarding a website and API for trading property information had no testers, but had continuous build and deploy with even more user oriented test cases that I could ever grab. (see: Fell in the trap of total coverage)
The general approach to Shift-Left is that “checking” moves earlier in the cycle in form of automation. More BDD, more TDD, more automated tests, continuous builds, frequent feedback and green bars. More based on “Test automation pyramid” (blog discussion, whiteboard testing video). Discussing the pyramid model reveals that testing and checking goes together in the lower levels too. I’m certain that (exploratory) testing happens among technicians and service-level developers; – usually not explicitly, but still.
To have “no QA” is not easy. Not easy on the testers because they need to shift and become more SET/SDET-like or shift something else (Shift-Right and Shift-Coach and Shift-Deliver). Neither is it easy on the team, as the team has to own the quality activities – as discussed in “So we’re going “No QA’s”. How do we get the devs to do enough testing?”
Testers and test managers cannot complain, when testing and checking is performed in new ways. When tool-supported testing take over the boring less-complex checks, we can either own these checks or move to facilitate that these checks are in place. Similarly when the (exploratory) brain-based testing of the complex and unknown is being handed over to some other person. Come to think of it I always prefer testing done by subject matter experts in the project, be it users, clients, testers or other specialists.
We need to shift to adapt to new contexts and new ways of aiding in delivering working solutions to our clients.
[…] Trending: Shift-Left […]
LikeLike
[…] trend goes along with Shift-Coach, Shift-Left and Shift-Deliver discussed separately. Initially I considered shift-right to be regarding […]
LikeLike
[…] I discussed Shift-Deliver, Shift-Right, Shift-Left and Shift-Coach at Nordic Testing Days 2016 during the talk “How to Test in IT operations“ […]
LikeLike
[…] https://jlottosen.wordpress.com/2016/10/10/shift-left/ […]
LikeLike
[…] It is not about the test cases any more, it’s about being part of a team – that delivers an IT solution to the business. First of all, if it’s just about the test cases then it is a race to the lowest paid off-shore location, a run to the bottom in repetitiveness and mechanic activity. Checking! with more focus on crossing the t’s and dotting the i’s. We have tools for that now – the plates are shifting. […]
LikeLike
[…] Trending: Shift-Left […]
LikeLike
[…] with no prior knowledge. Often the SME is the best tester available. I see this happening in a shift-left setting – but also in settings with a heavy user and business involvement. Like SAP releases to […]
LikeLike
[…] the business analyst / product owner (See The domain expert is the tester) as they are doing Shift-left. Similar to an agile or scrum coach, my approach was to look at it as a change in the way of […]
LikeLike
trackback: DevOps is cool, but get involved in OpsDev for Test Environment Management too! http://www.plutora.com/blog/opsdev-test-environments-management
LikeLike
[…] are strong trends that much test engineering is a developers discipline and that management of testing is more about coaching. Still some development organisations strive […]
LikeLike
[…] than testing specialists punching test cases. The testing activity as such, has shifted (both left and right), and testing is being done by many more roles than “testing people”. […]
LikeLike
Implementing these practices can greatly improve the reliability and efficiency of our testing processes. It’s essential to focus on implementing these practices to reduce cost of quality. I did some research around shift left testing and have included my findings here: https://testmetry.com/shift-left-testing/
LikeLike