Inserting Conditional Blocks

Qualitia users can add conditional blocks using the ELSE-IF button.

Task Level Conditional Blocks

On the task editor screen, click (Add Conditional Block button) to select any of the following conditions:

IF
Else IF
Else

Adding Expression for IF Step

Click the Add Conditional Block button, select IF.
You can add Else block within an IF block.

Forming Expression for IF /ELSE IF:

Expressions can be entered for IF and ELSE IF conditional step. User can use stored variables, environment variables as expressions.

Ensure that it is part IF/Else is added after an IF statement.
You can use Numeric, Boolean comparisons, string values, and arithmetic operators.
Environment variables and stored variables should be included in curly braces in expression.
User can save the execution status of last executed step as anyone of the following.
- Using $$_STATUS directly in expression
- Saving status of step {$$_STATUS} for use as an expression.
  User can save the execution status of a step in variable. This status can later be used as an expression of IF step.
- Saving execution status for future reference. You need to use StoreVariable Action and in the second parameter column enter as "{$$_Status}". For more information about $$_Status and similar variables, refer to Qualitia System Variables.

Examples of Expressions:

The following are some examples of valid/invalid expressions, assuming var1 and var2 as stored variables.

Note

The static or dynamic string data used should always be enclosed within double-quotes.
The expression, having string as data, should always be enclosed within double-quotes.
Boolean values are case-sensitive and should be used in lower case.

Data type	Example	Valid/Invalid
Any	var1=2 var1=var2 var1*=1 var1+=2 var1++ var1=var2+2==10	All are invalid as assignment operator is not allowed in expression
String	""India"=="India"" ""{var1}"=="{var2}"" India==India {var1}=={var2} (var1 and Var2 are stored variables containing string values)	Valid Valid Invalid (The string data passed not specified in quotes "" also the whole expression is not inside "") Invalid (Variables containing string data are not specified in quotes "" also the whole expression is not inside "")
Integer	1==1 {var1}=={var2} ""1"=="1"" ""{var1}"=="{var2}"" (var1 and Var2 are stored variables containing integer values or numbers)	Valid Valid Valid Valid
Float	1.254==1.345 {var1}=={var2} (var1 and Var2 are stored variables containing Float values)	Valid Valid
Boolean	true==true false==false TRUE==TRUE FALSE==FALSE {var1}=={var2} (where var1 and var2 can have value either true or false)	Valid Valid Invalid (Boolean values are case sensitive. Boolean values should be passed in small case). Invalid Valid
Logical operators	(var1=true , var2=false) {var1}&&{var2}==false {var1}\|\|{var2==true !({var1}&&{var2})==true	Valid Valid Valid
Arithmetic Operators	1+1==2 1-1==0 2*2==4 8/2==4 9%2==1	Valid Valid Valid Valid Valid
Relational Operators	1==1 1!=2 {Var1}<{var2} {var1}>{var2} {Var1}<={var2} {var1}>={var2}	Valid Valid Valid Valid Valid Valid
Bitwise Operators	(var1=60 , var2=13) ({var1}&{var2})==12 ({var1}\|{var2})==61 {var1}&{var2}==12 {var1}\|{var2}==61 ({var1}^{var2})==49 {var1}^{var2}==49 ~{var1}==-61 ~~{var1}==-61 ~~({var1})==-61 {var1}<<2==240 {var1}>>2==15 {var1}>>>2==15	Valid Valid Invalid (Outer () are required,otherwise interpretation goes wrong and it may return false) Invalid (Outer () are required,otherwise interpretation goes wrong and it may return false) Valid Valid Invalid (~ itself is a qualitia special character) Valid (escape character ~ is followed by complement operator ~) Valid Valid Valid Valid
Special Characters	Using Qualitia Special characters: ""a~_{xyz"== "a}~xyz"" ""a~^xyz"== "a~^xyz"" ""a~{xyz"== "a~{xyz"" ""a~{xyz"== "a~{xyz"" Always use escape character ~ before qualitia special characters ~,^,{,} For any other character no escape character is required. e.g ""as#gh%ff"==" as#gh%ff""	All are valid

Adding the Task Step on the TC Screen

You can add the task step using the Add button. After adding the task step, you can add conditional blocks with or without expressions to that step.

Test Case Level Step (TC step) on the Test Cases Screen

In case you want to avoid adding a task for a single step, you can add TC step. You can then add object, action, and parameters to a TC step just like a task step.

The TC step can be added at any position, after or before a task or even as a first step of test case.

To add TC step:

Focus on task and click the TC Step button. You can then use Up and Down buttons to move the step up or down.

Adding A TC Step and Task Step

Storing Execution Status of TC Step

The execution status of TC step can be stored the same as the task step.

ELSE IF Blocks on the Test Cases Screen

On the Test Cases screen you can add conditional blocks to task and Test Case. The Test Case level ELSE-IF blocks can contain tasks and the contained tasks in turn can have task level ELSE-IF blocks.

Adding the ELSE-IFBlocks to Test Case

You can add the TC or Task condition using the ELSE-IF button from the Test cases screen.

To add TC or Task Condition:

Select TC Step/Task after which you wish to add TC level conditional block.
Click Add Conditional Block >TC Condition > IF.
.Select IF step of block, click the TC Step button to add TC step.
Select recently added TC Step:
1. Click Add Condition Block >TC Condition >ELSE IF to add TC level ELSE IF block.
2. Click Add Condition Block >TC Condition > ELSE to add ELSE block.
  Note: If you want to add an Else-If or Else condition, it must be added after the If condition.

Adding Tasks in Test Case Level ELSE-IF Blocks

You can add new tasks or import tasks from the existing library of tasks inside the conditional blocks.

To add tasks in TC level ELSE-IF blocks:

Select TC Step/Task after which you want to add TC level conditional block.
Click Condition >TC Condition > IF.
Select IF step of block and then click New to add new task or Import to add the existing task to the conditional block.
To add Tasks to ELSE-IF or ELSE blocks, select the ELSE-IF or ELSE step of the conditional block and then click New or Import.
Note: If you want to add an Else-If or Else condition, it must be added after If condition.

Adding ELSE-IF Blocks to Task in TC

You can add the conditional blocks particularly for task.

Note: If you want to add an Else-If or Else condition, it must be added after If condition.

To add conditional blocks to a task from the Test case:

Create a new test case and add required tasks to it.
Select the step after which the conditional block needs to be added, or the task row to which the block needs to be added.
Click the Add Conditional Block button > Task Condition > IF.
Once If block is added to task, ELSE IF or ELSE blocks can be added by selecting proper task step and using the ELSE-IF button.
For adding expression, double-click IF or ELSE IF.
Use the syntax of expression is as described 1577844752.

Execution flow of conditional (ELSE-IF) blocks will be as follows:

Qualitia validates expression entered by the user and checks if the expression is empty or contains assignment (for example, if user entered a=b which is invalid). Expressions should not have assignment, users should use "==" operator instead. Hence {a}={b} is invalid expression.
Rest of the syntax and semantics is checked during the actual execution of test case.
You must enclose stored variables, environment variables in curly braces (for eg: {a}=={b}, or ($$_Status}==0.
Consider the following test case level conditional block:
1. OpenUrl
2. IF {$$_Status}==0
  Task1
  Task2
3. ELSE IF {$$_Status}==1
  Task3
4. ELSE
  Task4
5. END IF

If during execution, the step OpenUrl is successful, then Task1, Task2 is executed.

If the step OpenUrl fails, then Task3 is executed.

If the OpenUrl has execution status other than 0 or 1, Qualitia executes Task 4.

Qualitia's Behavior in case of Invalid Expression:

If the expression is invalid, for example, expression has stored variables referred but not declared, or the syntax of expression is invalid then the test case is considered to have an error and Qualitia will stop execution of test case.
When execution is triggered using the Dry Run button from the Develop tab and if the expression is invalid, Qualitia stops execution of test case.
When execution is triggered using the Run Now button from the Execute tab and if the expression is invalid, Qualitia executes next test case. If there is only one test case, execution will be stoppped.

In all such cases, Error log in reports will explain the reason of execution failure so that users can take corrective actions.

Browser not supported