Skip Operations

Keyword: JUMPBY

Description: This keyword or action instructs ICE to skip the steps as per the input given and execute the further steps.

Keyword	Input Syntax	Output Syntax	Supported Input Formats
jumpBy	<Count of steps>	NA	Text Static values/ Dynamic Variables Input can be positive or negative value

Note:

1. If input is positive, then the execution skips the specified number of steps in the input and executes the steps present after that.

2. If input is 0, execution continues in sequential order.

3. There are certain rules to be followed in JumpBy –ve. Please go through “JumpBy Negative” screenshots given below.

jumpBy Negative Scenario

jumpBy Positive Scenario

Find the snippet of the keyword below:

In In the above example after the test case debug, it skips 3 steps and execute from step number 9.

Keyword: JUMPTO

Description: This keyword or action instructs ICE to jump to the test case specified in the input. Test case should be a part of the scenario which is being executed in the test suite.

Keyword	Input Syntax	Output Syntax	Supported Input Formats
jumpTo	<Test case name>	NA	Text Static values/ Dynamic Variables

Note:

1. jumpTo target test case should be present as part of the scenario being executed in the test suite.

2. jumpTo is allowed forward/backward direction i.e. the jump can happen to a test case which is present in a position after/before the current test case in the scenario.

3. It works only in execution and not on debug.

4. “stop” keyword can be used to avoid executing the same test case multiple times.

5. “jumpTo” backward test case is supported only for Emerson CBU.

“jumpTo forward/backward flow”

Consider there are two scenarios in a test suite and two test scripts in each scenario.

1. In Scenario 1, during execution when it encounters “jumpTo” in Step 2, the control will jump from Step 1 of Script 2 (as given in the input).

2. Once it completes with the execution in Script 2 (Scenario-1), the control will move back to Step 3 of Script 1 and execution will continue till Script 2 and then Scenario 2.

3. Tester should add “stop” keyword in Script 1 to avoid re-execution of Script 2. When it encounters “stop” keyword, the execution of Script 1 will stop and will continue from Sript 1 of Scenario 2.

Find the snippet of the keyword below:

In In the above example after execution, when the jumpTo keyword is encountered, then the control moves to “Date_Operations_Stop” testcase and execution continues. Upon completing execution of “Date_Operations_Stop” testcase, the control comes back to original testcase and the remaining steps are executed till stop keyword.