addressalign-toparrow-leftarrow-rightbackbellblockcalendarcameraccwcheckchevron-downchevron-leftchevron-rightchevron-small-downchevron-small-leftchevron-small-rightchevron-small-upchevron-upcircle-with-checkcircle-with-crosscircle-with-pluscrossdots-three-verticaleditemptyheartexporteye-with-lineeyefacebookfolderfullheartglobegmailgooglegroupshelp-with-circleimageimagesinstagramFill 1linklocation-pinm-swarmSearchmailmessagesminusmoremuplabelShape 3 + Rectangle 1ShapeoutlookpersonJoin Group on CardStartprice-ribbonprintShapeShapeShapeShapeImported LayersImported LayersImported Layersshieldstartickettrashtriangle-downtriangle-uptwitteruserwarningyahoo

Efficient and Effective Test Design

Justin Hunter of Hexawise will be leading this discussion. Justin Hunter is the founder and CEO of Hexawise
He led combination testing efforts at Accenture (a 180,000 person management consulting and
IT firm), and decided to form Hexawise after a couple dozen combination testing projects
made it clear that: (1) combination testing consistently demonstrated compelling efficiency and
quality improvement benefits, and (2) that even sophisticated Fortune 100 firms were not yet
using combination testing tools or methods.

Here is the agenda:

I. Welcome (Bob Galen)
II. Introduction / Executive Summary (Justin Hunter)
-What challenges does combination testing solve?
-How does combination testing work?
-Where can it be used and what benefits does it deliver?
-What are critical success factors and general lessons learned from 2 dozen projects?
-Why isn’t this method of test design more well known and more widespread?

III. How the Proof of Concept Pilots Were Conducted (Bob Galen)
-Structure of Pilots
-- “2 testers in a room w/ Hexawise vs. 4 testers in a room w/out Hexawise”
-Three hypotheses that were tested in each case study:
-- No. 1 - Test design speed: savings of at least 30%
-- No. 2 - Test execution speed: savings of at least 25%
-- No. 3 - Cost of defect resolution: savings of at least 20%
IV. Panelist Discussion
-Summary of pilot projects - What kind of testing projects did the panelists choose? Why?
-Findings for each of the three hypotheses - Were targeted savings achieved?
-Ease of use / change management - How easy was it to learn? implement?
-Lessons learned - What went well? ... not so well? ... any surprises?
-Turning the “speed v. quality” dial - How will panelists use the efficiencies created?
-Implications - Will panelists use Hexawise again? Why? Why not? Where?

Panelists include: Lester Bostic and Justin Hunter. Others coming soon....

Join or login to comment.

  • Justin H.

    I posted the presentation on my blog at:

    (OK, I'll stop posting now... starting to get self-conscious about the excessive number of my posts on this page).

    If anyone every has any questions about applying these test design techniques, please don't hesitate to reach out to me at justin dot hunter a@t hexawise daht com. I'd be more than happy to pick up the phone and talk. I hope you found the topic to be applicable to what you are doing.

    September 18, 2009

  • A former member
    A former member

    Excellent presentation. Great idea and product. Good questions from the group. Very engaged. Glad to be a new member.

    September 17, 2009

  • Justin H.

    If anyone wants free access to the Hexawise test design tool highlighted in the presentation, please sign up here:

    September 17, 2009

  • Justin H.

    Also, Bob asked about coverage achieved through pairwise testing. Here is the (very good) article I mentioned:

    3 examples from it:

    "The pairwise tests gave over 90 percent block coverage."

    "... cover 97% of branches with less than 100... testcases, as compared to 27 trillion exhaustive testcases."

    "29 pair-wise tests gave 90% block coverage ..."

    - Justin

    September 17, 2009

  • Justin H.

    If anyone has any questions before or after the presentation, I would be happy to answer them. Also, if you would be interested in joining the panel discussion and/or conducting a proof of concept pilot project that could take as little as 1 week start to finish, please let me know. Lester Bostic from Blue Cross Blue Shield will be talking about his recent experiences . Thank you. Justin

    September 16, 2009

20 went

This Meetup is community funded


Member dues are used to:
  • Cover Meetup costs
  • Provide supplies or equipment

60 day free trial

No credit card required

After the trial you must pay dues to continue attending Meetups.

Cancel dues at any time.

Dues are billed each year.

People in this
Meetup are also in:

Sign up

Meetup members, Log in

By clicking "Sign up" or "Sign up using Facebook", you confirm that you accept our Terms of Service & Privacy Policy