(Lessons Explaining How to Use Hexawise Features) Instructions for the Expert ➜ Guru AchievementsHow do I "force" Hexawise to include required scenarios and manage requirements traceability?

How do I "force" Hexawise to include required scenarios and manage requirements traceability?

This lesson explains how to use the Requirements feature of Hexawise. If you want your tests to include specific combinations of Values, this one is for you.

You look at your tests and feel "something is missing."

You want to make sure that the Hexawise tests include a test for a required business rule. Like this one:

Requirement: (#2947 - Reject Certain High Risk Flood Zone Applications)

The business rule you want to test reads: "If the applicant has a low salary and a low credit rating applying for a house in a flood zone and the house will be used as a vacation residence, then reject the application immediately."

Ask yourself: "How many test inputs do I need to trigger this business rule?"

To test this business rule, you you will need to have these specific 4 Values included together in a single script:

  • Customer status must be Regular
  • Loan to value ration must be 90%
  • Loan amount must be Large
  • And the property needs to be In a Flood Zone

(At the risk of stating the obvious here, if this analysis shows that your plan does not yet include all of the specific Values needed to test the business rule, you may need to go back to the Define Inputs screen and add one or more Parameters and Values.)

Go to the Required screen and add your requirement. It's simple:

Both of these steps are optional:

  1. Add the name and/or number of your requirement
  2. Add the expected result for your requirement.

Select only the Values you need to trigger your requirement or business rule.

That's it! When you create your tests, your requirement will appear in a newly-generated set of tests!

Suggested usage tips:

  1. This feature is not just for "official requirements." Consider including one test case in your Hexawise-generated tests that contains the most common Value for each Parameter.
  2. As shown in the example above, you don't need to specify every Value. In fact, it is better if you only specify the Values needed to trigger the requirement. That way, as much variation as possible will be included in your Hexawise-generated tests.
  3. Keep the concept of "Expected Results" clearly separate in your mind from ordinary Parameters and Values. Treat Expected Results very differently from the Parameters and Values you enter into your plans. Do not enter the Expected Result value in the Define Inputs screen. The only place you should enter the Expected Results is in an Expected Result field. These Expected Results fields are located on the Define Inputs screen and the Auto-Scripts screen.
  4. Use this feature selectively. Remember that many combinations will automatically appear in your Hexawise-generated plans without requiring you to do anything special. If you have a requirement that only requires two Values to appear together, for example, that requirement will already be satisfied automatically whenever you create a 2-way (AKA "pair-wise" set of tests). If you're creating a 2-way set of tests, you would only need to use this special feature when you're trying to ensure that 3 or more specific Values get tested together in a single test case.