Case Study Highlights: How Hexawise Takes the Guesswork Out of Testing

One of the most common pitfalls in software testing is performing too few tests. An inadequate number of tests can lead to gaps in coverage, which allow defects to go undetected until they are discovered by a tester later in development or an end...

How Hexawise Puts an End to "Garbage In, Garbage Out"

“Garbage in, garbage out” is a phrase commonly used in software development to refer to a basic limitation of all software tools: if the user’s inputs are flawed, inaccurate, or nonsensical, then the application’s output will be as well. Garbage...

Hexawise Tests Are Robust and Thorough

Hexawise generates different kinds of tests - by design. The objective behind a set of Hexawise tests is different than that of most manually-designed test sets.

Rather than trying to “Confirm that X works correctly,” Hexawise tests are focused...

Kathleen Poulsen of Fidelity Investments on Using Hexawise to Improve Software Testing Results

The highlights from a presentation by Kathleen Poulsen, Lead Software Engineer in Test at Fidelity Investments, at the StarEAST 2017 testing conference discussing the use of Hexawise at Fidelity Investments and some of the significant benefits of implementing Combinatorial Test Design at scale.

Testing Smarter with Alan Page

An interview from our "Testing Smarter with..." blog post series with Alan Page, a software tester (among other roles) since 1993 who spent over twenty years at Microsoft working on a variety of operating systems and applications in nearly every Microsoft division.

84% of Software Defects Found in Production Could Have Been Found Using Pairwise Testing

Studies show that 84% of defects found in production could have been found by testing every pair of parameter values. Hexawise helps you find these pairwise defects before they reach users.

How to Pack More Coverage Into Fewer Software Tests

A detailed dive into the considerable benefits achieved by using Hexawise and how these benefits come to be.

What do people mean when they say "it works"?

Unpacks the commonly-used phrase - "It works" - and why just testing that something "works" by passing a given set of requirements is never enough.

Start with a Small Test Plan and Add Details as Necessary

Introduces the "Goldilocks Rule" for guidance on how much information to include in a single Hexawise test plan.

Should I Use One Test Plan or Multiple Plans?

Provides helpful guidance on when it might make sense to split your single Hexawise plan into multiple different plans due to different "Verb and Noun" ideas within the same set of tests.