All Collections
Hexawise Features
Scenario Generation
Preserve test conditions with the "Freeze Tests" feature
Preserve test conditions with the "Freeze Tests" feature

Learn how to ensure specific scenarios do not change even when you are updating your model

Conor Wolford avatar
Written by Conor Wolford
Updated over a week ago

What if we want to test an Airplane Ticket Reservation scenario, but need to edit it after completing some testing?

We will use a version of the sample model "A) Airplan Ticket Reservation" for this article. After going to the Scenarios screen, here's what our table looks like.

Click the "Freeze these Scenarios" Button

On the Scenarios screen, click the "Freeze these Scenarios" button located in the top-right just above your first created test. 

You will be faced with the following warning message, reminding you that freezing your test cases should only be done when there is a valid reason to do so. If there is a valid reason to freeze the tests and you do wish to continue, click the "Freeze" button.

Once you click "Freeze," your existing test cases will be "frozen" as Forced Interactions. 

Here's what the Forced Interactions page looks like now. All of our tests have been "frozen" as the combinations of forced parameter values!

How is this useful?

Let's add another parameter, "Amount of Luggage". At this point, we may have already run some of these scenarios, so we don't want to have to re-do any of them, even if Hexawise could reduce the total number. By freezing the previous 13 tests, Hexawise will keep them as they are, and simply add a couple scenarios to pair all of the new values - the numbers of luggage - with every other value. 

Here are the new tests. Note the initial 13 combinations are still present. We've simply added a few more.

Here's what the differences could have looked like if we had not frozen our initial 13 tests.

Notice how Test Case 3 contained the following while frozen:

  • USA

  • India

  • Coach

  • None

  • 1

  • More than 1

  • 2 or more

Without freezing, the third row could contain the following after the new parameter was added and the table was "freshly" regenerated:

  • USA

  • India

  • First

  • Selected

  • 1

  • 0

  • 2 or more

Therefore, we would have needed to re-run our initial scenarios. 

Important: Keep in mind that Freezing does not affect the functions built on top of values (e.g. value expansions, ranges). Those elements may show different choices when a frozen set of scenarios goes through regeneration. The more value expansions there are and/or the wider ranges are, the more likely you will see discrepancies.

What if we want to "unfreeze" our scenarios?

Easy! We can do so by navigating to the Forced Interactions page and simply clicking the "Unfreeze" button above the table. 

Did this answer your question?