Why Today's SDLC Requires a New Perspective On “Test”

Apr 16, 2015

Posted by Parasoft

In response to today's demand for "Continuous Everything," the software delivery conveyer belt keeps moving faster and faster.  However, considering that testing has been the primary constraint of the software delivery process, it's unreasonable to expect that simply speeding up a troubled process will yield better results.

(I Love Lucy fans: Just think of Lucy and Ethel at the candy factory, struggling to keep pace as the conveyer belt starts putting out chocolates faster and faster.)

In most organizations, quality software is clearly the intention, yet the culture of the organization drives behavior that increases the risk of exposing faulty software to the market.  Most software quality efforts stem from a bottom-up approach to testing, which is focused on adding incremental tests to validate new functionality. 

This approach is no longer sufficient for today’s accelerated release cycles—where faulty software has a direct impact to the brand and bottom line.  Releasing with both speed and confidence requires a definitive understanding of each application's distinct business risks and the probability of exposure.

In order to achieve this, we need a method to federate quality information from multiple infrastructure sources (source code management, build management, defect management, testing, etc.).  A Development Testing Platform is this central “system of decision” which aligns development activities with business expectations, providing insight and control over the process of creating quality software.  The goal is not only to reduce business risk but also dramatically reduce the number of defects that are introduced into the code base in the first place.

Gartner_DevelopmentTestingThe resources in the new Today's SDLC Requires a New Perspective on "Test" package, featuring Gartner Research, provides software development leaders recommendations for ensuring that SDLC acceleration does not undermine existing functionality or negatively impact the user experience. Read it to learn:

  • Why the traditional "bottom-up" approach to testing is too risky for today’s accelerated release cycles

  • How your existing tool set can provide a new level of SDLC insight and control

  • How to tell if development's innovations are satisfying business expectations

  • The top 4 challenges with automated testing

  • Best practices for improving code base stability, structuring automated tests, and building test suites for legacy code

 

New Call-to-action