Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

How Hyper-Testing Helped a Company Sprint Ahead with End-to-End, Agile Testing

DZone's Guide to

How Hyper-Testing Helped a Company Sprint Ahead with End-to-End, Agile Testing

Check out how hyper-testing brought an advertising software company great results by throttling and optimizing the normal continuous testing process.

· Performance Zone ·
Free Resource

xMatters delivers integration-driven collaboration that relays data between systems, while engaging the right people to proactively resolve issues. Read the Monitoring in a Connected Enterprise whitepaper and learn about 3 tools for resolving incidents quickly.

A leading provider of advertising management software used a generous dose of Hyper-Testing to wholeheartedly embrace a commitment to Quality Engineering and achieve wonderfully productive business outcomes.

The only constant in today’s digital world is change. When consumers expect the next big thing within the next hour, products go from concept to market at lightning speed, and time-to-market can mean the difference between winning and losing.  You need to continuously create new sources of customer value while also increasing the speed of delivery. Otherwise, you risk waking up one day to realize—like Blockbuster, Kodak, and Nokia—that although you did nothing “wrong,” you have somehow met your demise. To keep up with today’s rates of change, organizations are now embracing agile and DevOps-driven practices. However, testing practices still remain sluggish because of traditional testing processes and tools that are not able to comply with speed.

This is precisely the challenge that this company was grappling with. Legacy testing processes not aligned with CI/CD were throttling the release of quality software at high speed. High turnaround time was leading to customer dissatisfaction and impacting their ability to provide services to a global customer base. To succeed in a world where even the smallest releases can have a huge impact on the end user experience, they needed testing to be as dynamic and efficient as their agile development processes.

Yet, they had done precious little to update processes or arm testers to face the time pressures of modern development. As the software kept growing, testing each sprint became a problem. Testers would have to test an increasingly expanding set of features, verify bug fixes and perform regression testing—all within the sprint timeline. Very soon the test team started getting bogged down and overburdened.

Hyper-Testing: The Hero

Hyper-Testing is essentially an effective full-cycle test strategy that combines some great tools and techniques to enable testing at digital speed and scale.

The idea is to employ an end-to-end approach focusing on innovative tools, automated QA processes, and test optimization alongside test environment consolidation to ensure maximum test coverage and quality at reduced costs. It helps to create complete visibility across the software development lifecycle facilitating an end-to-end view of defects and driving targeted improvements.

How Did Hyper-Testing Help?

The goal was to put testing techniques in place throughout the entire lifecycle to ensure that testing no longer remains a bottleneck, and teams can keep up with continuous quality. The process and vision of end-to-end, agile testing were coupled with the tools and automation to support that strategy and scale and realize the value.

Agile and continuous testing can create an enormous amount of added value for organizations. However, in the absence of end-to-end automation, it can be very taxing and create a lot of overhead. Automation enables companies to test early, test fast, and automate easily at every stage of product development.

As part of the Hyper-Testing approach, the company leveraged AFTA (Aspire’s Framework for Test Automation) as a critical enabler for Continuous Delivery and agile software development. The powerful automation framework integrated with the continuous testing tools to really power the continuous testing process. It helped them significantly cut down testing efforts, minimize test maintenance and also reduce false positives.

On top of automation, a multitude of other key methodologies were employed for a continuous testing workflow; in other words, a full spectrum of well-defined processes to optimize functional testing across all layers of the application and technology stack. Rigorous system integration QA was also carried out to ensure application functionality performance in an integrated environment through module testing and interaction with various external systems. Through Hyper-Testing, they were also able to ensure a comprehensive performance management approach in terms of evaluating, defining, benchmarking, monitoring, and managing performance and reliability of systems across a multi-technology, multi-platform, multi-network setting. It not only provided a clear insight into their application performance but also helped them gather and evaluate data to uncover the root cause of performance issues and take preventive measures.

In keeping with the spirit of Agile and DevOps, they formed a TechOps research team, consisting of developers, DBA, and QA personnel to probe technical and performance issues occurring in production and resolve problems faster.  Hyper-testing also enabled informed release decisions and Continuous Improvement with the help of comprehensive QA dashboard/metrics, which in turn helped to improve visibility and find defects early. Another noteworthy point was the regular creation of Release Health Index (RHI) reports that helped accelerate Go/No-Go decision making.

A lot has happened since Hyper-Testing was adopted. Here are just some of the benefits have they seen so far:

  • Streamlined their testing process
  • Shortened testing feedback cycle times
  • Improved collaboration between distributed teams
  • Accelerated time to market
  • Reduced Cost of Quality (COQ)

The Future Through the Lens of Hyper-Testing

The litmus test for any methodology isn’t really about whether or not it produces repeatable results. Hyper-Testing principles are proven and they tend to produce solid business outcomes in any software project.

One of the most critical aspects of this approach is that it goes beyond mere "quality assurance" with the help of process monitoring and reactive testing frameworks. There's an implicit acknowledgment that for software to be effective, it is important to consistently test and assure quality throughout the software development lifecycle. There would almost always be some defects that leak out into production, but when feedback loops and processes are automated, the focus will be on defect prevention and assurance of Continuous Delivery confidence. Quality is viewed as something that is in a constant state of change and improvement. Hyper-Testing is, therefore, more of a commitment to Quality Engineering and customer satisfaction.

To learn in detail about how organizations can implement quality engineering principles and apply Continuous testing through a templated approach, with detailed tools guidance, join us for a discussion on “Quality Engineering through Hyper-Testing” on May 2nd and May 3rd  at STAREAST. Register your spot here

3 Steps to Monitoring in a Connected Enterprise. Check out xMatters.

Topics:
testing ,continuous testing ,quality engineering ,agile testing ,quality assurance ,test automation ,agile ,hyper-testing

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}