Applause Survey on Left Shift Security Reasons and Obstacles for Shift-Left Testing
Shift-left testing is supposed to speed up release cycles in DevSecOps scenarios, but the prerequisites for a successful introduction are not given everywhere. Applause has identified the main obstacles in a survey.
Shift-left testing brings benefits, but many companies complain about productivity losses among their developers. (Image: ThisIsEngineering / Pexels )
The Shift Left describes the strategy of pushing security processes and testing further to the left on the timeline of the software Development lifecycle. There was broad consensus in the context of a recent survey by Applause that such a left shift brings great benefits.
Six out of ten respondents saw a particularly large benefit in reducing bugs in the end product, while 44 percent also highlighted the cost savings for later bug fixes. 38 percent of over 1,800 QA, product, engineering and DevOps professionals also believe in faster release of new features and builds.
However, many companies still have to remove obstacles that stand in the way of their shift-left strategies. For example, in the survey, 45 percent of participants complained that their developers are too busy with programming. Another 37 percent complained that development and quality assurance are still separate.
More than half of the respondents whose employers have already completed the Shift Left said that testing affects developers ‘ productivity (52 percent). In corresponding large companies, development teams often spend an entire working day a week only testing new functions (44 percent).
With In-Sprint Testing, Applause offers a technical way to move testing to an earlier stage in the SDLC, allowing smaller code sections to be tested faster and in an iterative model. The offer is part of the Product Excellence Platform of Applause.