How to best use Hexawise in agile model?

  • 1
  • Question
  • Updated 4 years ago
  • Answered
I have a general question raised to me by one of the test lead. The Test Lead is coming from a waterfall model, and their beginning to shift towards an agile development approach. Since their Test Strategy is still not finalized at this time, she asked if Hexawise has been successful already in an agile setting. Will the same test process be used regardless if it's a waterfall or an agile methodology? Are there similarities and differences to consider? How best to use the tool in an agile setting?
Photo of Ed

Ed

  • 25 Posts
  • 0 Reply Likes

Posted 7 years ago

  • 1
Photo of Justin Hunter, Hexawise Founder

Justin Hunter, Hexawise Founder, Founder and CEO

  • 246 Posts
  • 15 Reply Likes
Ed,

Good question. Yes, Hexawise is widely used in both Waterfall and Agile projects.

Agile projects involve short sprints in which new features are added to existing functionality. These sprints are often a couple weeks long. In such situations, it is important to be able to create tests quickly. Hexawise is extremely good at accomplishing exactly that.

Let me explain by way of an example. About a month ago, a Hexawise user named Sandeep asked how Hexawise could be used to create tests for an insurance ratings engine. As seen at http://www.getsatisfaction.com/hexawi... I was able to create a sample set of 37 2-way tests within 20 minutes.

Now lets imagine that a sprint creates 2 new features that we'd like to test in combination with the existing test inputs in the existing plan. Let's assume "Feature 1" is a new ability of the application to handle input coming in from three sources: (1) web, (2) agent, and (3) call center. Let's assume "Feature 2" is a new ability of the application to handle Group Discounts. The Group Discount parameter will have 3 categories of values as well: (N/A) for people who aren't able to claim them, "Private company," and "Government / Public."

It is now 10:45 PM by my computer clock right now. I'll be back after I make the changes to the tool and create new tests.
Photo of Justin Hunter, Hexawise Founder

Justin Hunter, Hexawise Founder, Founder and CEO

  • 246 Posts
  • 15 Reply Likes
It's 10:49. I've logged into Hexawise, added the new features, and created another, completely different set of tests that achieve 100% 2-way coverage. Each value in the new feature is tested in at least one test with every other value in the plan.

Channel = Agent and Primary Applicant = Male? Covered in one of the tests.

Group Discount = Government / Public and Pre-existing Condition # 5 = Y? Covered in at least one of the tests.

Any value you can think of and any other value you can think of? Covered in at least one of the tests.

It took less than 4 minutes to create this new set of tests and incorporate the new features. It is an extremely attractive benefit of using Hexawise that is excellent for both Waterfall projects (which inevitably have late-breaking requirements changes) as well as Agile projects (where late-breaking feature additions are expected to happen as part of the process).

New features were added in Hexawise's "Define Inputs" page, as shown below:



Once those two new features are added, all you need to do is hit the "Create Tests" button to create an entirely new set of tests. It turns out that there are 1.7 trillion different possible combinations of test input values in the plan. Hexawise is able to identify, in seconds, the 37 tests (from 1.7 trillion) that are most likely to trigger defects in the application. A portion of those 37 2-way (AKA pairwise software tests) are shown below.



Another aspect of Agile software testing is that it often relies much more heavily on automated testing, TDD, and continuous integration. Hexawise is compatible with all of these software testing approaches. Hexawise test conditions can be easily exported to Excel and, from there, imported into any test management tool.
Photo of Michelle

Michelle

  • 3 Posts
  • 0 Reply Likes
The waterfall model is quite different from agile testing. agile works in short sprints while waterfall is a whole defined process.