Learn how to easily create detailed, consistent execution instructions with conditional expected results for your manual testing efforts.
Note: to learn more about DesignWise Automate and Gherkin scripting, please refer to the "Usage" button in the top right of the Scripts → Automate screen.
With DesignWise’s Auto-Scripts feature, you can quickly transform optimized test data like this…
… into customizable scripts. You can even add automatically-generated Expected Results to your steps if you want to.
Creating Auto-scripts in DesignWise is similar to that. Instead of adding adjectives and nouns into pre-formed sentences, however, you’ll be more like the author of the Mad Libs sentences themselves. You need to:
First, navigate to the Scripts -> Manual Auto-Scripts screen and (optionally) add instructions to be completed before execution for all these scenarios begins. (i.e. the details in the "Start" field have to be common across the board).
Next, click on the “pencil” icon to enter instructions for your first test step. Alternatively, you may click the text already present for the step. Enter detailed instructions for a tester for each step. For now, type Mad Libs-like sentences, as shown below with blank lines to indicate where Values are to be inserted.
As shown above, for example, you will want to type the words that will remain the same from test to test and leave 3 blanks (one for each place that Values will change from test to test):
Next, replace those blank lines with the appropriate Parameter names.
Don’t forget to save each step before you add your next one! Thankfully, DesignWise notifies you under the last edited step that there are unsaved edits. Click on different test cases at the bottom half of your screen (preview section that mirrors Scenarios screen) to see how your script steps will change. Finally, in the “Finish” section you may want to add some instructions that will appear only once at the end of all of the scenario scripts.
In the tests shown above for example, we might want to include this Expected Result every time the necessary values appear together in a test case:
When a customer flies to India, make sure the special "Incredible India" discount is applied.
In the Scripts -> Manual Auto-Scripts screen, find the specific test step you want to add your Expected Result to and highlight it
You’re setting up a simple “when / then” rule here. Note that you’re not restricted to rules with just 1 positive condition - you could also create a rule that reads “IS NOT” (click on “is” between dropdowns to switch the rule type).
If WHEN selection is blank, the expected result from THEN field will apply to that step in all test cases, regardless of the test data.
Lastly, you can put parameter names with { } syntax inside the THEN statement – this is typically valuable in the validation use cases where the step would say “Enter X as {X}” and the expected result would say “Validate the X is shown as {X}”. Parameter names do not have to match, in case you have already included actual expected results on the Parameters screen. In such cases WHEN conditions are often left blank.
1. This feature is a partial solution for straightforward Expected Results. It primarily exists so that you won’t have to manually type many, simple expected results. It is not designed to handle especially complex rules that you might have.
2. Be sure you understand the similarities & differences between DesignWise’s Expected Results in the Auto-scripts screen, and Expected Outcomes in the “Forced Interactions” feature. There is a big, yet subtle, difference:
DesignWise Automate can leverage that last column on Forced Interactions directly as an internal variable.
If you want to define an Expected Result that requires 2 or fewer specific Values to appear in a single test script (and you’re creating pairwise sets of tests), use the Manual Auto-Scripts feature without additional prep work.