Lesson 15 Topic 5 Features
This article is a part of the Self-paced Learning Series for the Course: First-Hand Experience of Worksoft SaaS.Please refer to the link for more details on the Course.
Introduction of Worksoft SaaS Feature/Concept :: Lesson 15 :: Topic 5
1. 'Automatic Controls' in Bind Data tab of Run Definition
Automatic Controls on Executions can be set on Data Binding screen before executing any test runs. When failures occur, these settings provide you with control to determine what Worksoft SaaS should do when it encounters certain behavior.
Let's take an example of a Run Definition which has one or more test scripts that are parameterized. The Test Scripts bound to a data file will iterate the steps for each row in the data file. In case there is an issue with the AUT and the corresponding instruction fails, it may not make business sense to iterate through all the rows. Hence we can choose between the 2 options provided:
1.1 "Skip subsequent iteration after (number can be choosen from 1 to 5) consecutive failures"/"Skip subsequent iteration after 2 non-consecutive failures"/"Skip subsequent iteration after 2 consecutive iterations"
1.2 "Abort entire execution after consecutive failures"/"Abort entire execution after non-consecutive failures"/"Abort entire execution after 2 consecutive iterations"
2. While, For, ForEach:
When we have built automation using looping commands like 'While, For, ForEach' and the same command has been failing in all the iterations, then we can choose between the 2 options provided:
When we have built automation using looping commands like 'While, For, ForEach' and the same command has been failing in all the iterations, then we can choose between the 2 options provided:
2.1 "Skip subsequent iteration after (number can be choose from 1 to 5) consecutive failures"/"Skip subsequent iteration after non-consecutive failures"/"Skip subsequent iteration after consecutive iterations"
2.2 "Abort entire execution after consecutive failures"/"Abort entire execution after non-consecutive failures"/"Abort entire execution after consecutive iterations"
3. Asserts: When we use the 'assert' command for a mandatory verification on the AUT and if any assert command fails, then we can choose following options as controls for your execution
3. Asserts: When we use the 'assert' command for a mandatory verification on the AUT and if any assert command fails, then we can choose following options as controls for your execution
3.1 Skip to next scenario after _ assert failure within a Scenario
3.2 Abort entire execution after _ assert failure within a scenario "
In any of the execution settings, when we choose to abort tests instead of letting it continue and fail, you can save both capacity and also debugging time.
3.2 Abort entire execution after _ assert failure within a scenario "
In any of the execution settings, when we choose to abort tests instead of letting it continue and fail, you can save both capacity and also debugging time.