Test Studio provides built-in conditions for the test scenarios which cannot be covered by a simple sequence of actions. One of the available conditions is the if..else block to determine how to proceed the test based on a specific condition.
In this article you can find the following topics:
Tip
Check this step-by-step tutorial blog post on how to enhance your test scenarios with conditional steps.
1. Create a Web Test and click Record.
2. Navigate to www.random.org.
3. Set the Min field to 1 and the Max field to 2.
4. Click Generate.
5. Enable hover over highlighting by clicking Highlight Element in the Test Studio Recorder and hover over the Result box.
6. Click Quick Tasks and double click Verify - text contains '1'.
7. Disable hover over highlighting and minimize the browser.
8. Choose Conditions in the Step Builder and add if...else step.
Standalone version
|
VS Plugin
|
9. From the drop down in the IF step select the previously recorded verification.
10. Uncheck/Delete the verification outside the IF step, so it will not be executed (We have this verification already added in the IF step)
11. Bring up the IE recording window and navigate to www.google.com. Minimize the browser again.
12. Drag the Navigate to Google step into the IF step.
13. Bring up the IE recording window and navigate to www.bing.com. Minimize the browser again.
14. Drag the Navigate to Bing step into the ELSE step.
15. Save and Execute the test.
- If 1 is generated the if condition is evaluated as true and the steps in the if branch are executed. The steps in the else branch are skipped and shown as 'Not Run'.
- If 2 is generated the if condition is evaluated as false (for example, the target TextBox element contains the wrong content) and the steps in the else branch are executed. The skipped steps are in the if branch and are shown as 'Not Run'.
-
Note: if the condition of an if branch cannot be evaluated (for example, the target element for a TextContent verification cannot be located), the steps in the if branch will be skipped again, and will display a 'not-run' icon as if the condition is false.
To check if an element is present in the application DOM - a "wait on element" verification has to be used. It returns true/false output and if condition could be completed not braking the test execution. On the following image - if step 4 does not execute - the SecondLink element would not be added to the DOM and steps would continue in the else branch.
If step 4 is executed the SecondLink element would be added to the DOM and if condition passes normally as shown below.
