Carrie Puterbaugh's presentation at the Twin Cities Quality Assurance Association on using Hexawise to improve software testing at her organization (a large bank).

In one example she discusses in the video Carrie's team used Hexawise to create an optimized test suite and provided that to the software vendor to have them run it prior to delivering the software to her bank. In this example historically they vendor was finding 67% of the defects and Carrie's bank was finding 33%. Now that the vendor is using the Hexawise test suite the vendor is finding 98.5% of the defects and fixing them prior to delivering the software to Carrie's bank.

Based on these results her team was able to move staff off of testing this application and onto other testing needs of the organization. They are saving 90% of what they used to spend on QA on this project.

Another project she talked about was a high priority and high risk release that they used Hexawise on and achieved the highest quality software release they have ever had.

It was great... We were able to go to management and say "we reduced the amount of test cases we ran and we got a better quality application.

Carrie discussed how valuable Hexawise was to improving the regression testing they must do on their large number of applications. She also mentioned how much value Hexawise added by presenting software testing plan information in an easy to visualize way that greatly improved the discussions between her (as the software testing manager) and the business executives she interacts with.

Related: Large Benefits = Happy Hexawise Clients and Happy Colleagues - Kathleen Poulsen of Fidelity Investments on Using Hexawise to Improve Software Testing Results - How to Pack More Coverage Into Fewer Software Tests

By: John Hunter on Oct 3, 2017

Categories: Business Case, Customer Success, Hexawise, Pairwise Testing, ROI, Software Testing Presentations, Testing Case Studies

Hexawise helps team achieve the following qualitative benefits:

Hexawise Benefits MM

Not all of the benefits above can easily be quantified. So what should you do if you are tasked with creating a business case to support adoption of Hexawise? Simple:

  • Measure what happens when you create ~50 tests with your business as usual process; compare that to how long it takes to generate a set of ~25 tests with Hexawise.
  • Measure how long it takes to execute each sets of tests.
  • Measure how many unique defects you find executing each set of tests.
  • For typical findings, see these empirical benefit measurement studies.
  • Then put together a business case summary like the one below.
    • The summary focuses primarily on the objectively measurable efficiency savings you measured.
    • The summary also breaks out valuable qualitative benefits into separate line items (to prevent those valuable - but difficult to quantify - benefits from being forgotten about).

Hexawise - Finanacial Benefit Model 2013.10.xlsx at 2.23.05 PM

By: Justin Hunter on Aug 11, 2014

Categories: Business Case, Hexawise, ROI, Combinatorial Testing, Pairwise Testing