They are provided to help you understand different aspects of designing better scenarios. Sample models with small numbers of Parameters tend to be highly-simplified instructional examples. Others, with higher numbers of Parameters, tend to involve more complex Systems Under Test.

Hover over the model name and click the "Copy" icon.

Visit the major screens in different Sample Models:

Familiarizing yourself with and making changes to a few sample models is a great way to quickly learn about how this tool works.

Hexawise is a different kind of tool with different features compared to other software testing tools that you might be familiar with, so don't panic if things don't look familiar. We've designed a series of certifications and support articles to help you increase your test design skills, understand the tool's features, and - most importantly - become a more knowledgeable and powerful software tester.

Not only will you create tests much faster, you'll also create much better tests than test scenarios you would be able to select by hand. They will be more varied, less repetitive, and leave significantly fewer gaps in coverage.

Difference #1: Generating optimized scenarios takes only seconds

Count how many seconds it takes you to generate new sets of test scenarios once you have identified an appropriate set of test inputs. Faster test scenario is an obvious benefit, but having said that, experienced users value other benefits even more.

For example, the benefit of much more thorough testing coverage that comes from optimized scenarios.

Difference # 2: Generated scenarios always automatically minimize wasteful repetition, being as varied as possible.

The 10 test scenarios above are very different from most manual sets of test scenarios. Most manually-selected sets of test scenarios, for example, would either have far more scenarios that test similar paths through the system (e.g., Coach Class with 1 Adult flying from the United States multiple times) or simply contain far more unspecified values (often due to testers selecting the same value in test after test).

Difference #3: Manually-selected scenarios tend to leave many accidental gaps in coverage.

You can easily examine testing coverage achieved by your generated scenarios in your models. Simply go to the "Analysis" screen and click on the "Coverage Matrix" option to see the coverage achieved by your optimized scenarios.

Detailed comparisons between coverage achieved by optimized scenarios and coverage achieved by your company's "business as usual" test selection methods are eye-opening! We often help our clients do this analysis with real sets of tests. Unfortunately, sample models themselves cannot provide this level of insight to new users.

If you're a new user exploring sample models, it is enough for now to simply become familiar with the concept that optimized scenarios are especially powerful and efficient. And unlike manually-selected sets of test scenarios, these generated scenarios will not accidentally leave gaps in coverage. As you progress through our suggested achievements, you will learn more details about what exactly these coverage reports mean.

Finally, be sure to check the "Notes" for some useful comments and links about the Sample Models. This icon is present next to the Model Name at the top.
​

​