Sample Workflows

Real Life Use-cases where Workflow can be used

1. Make automation status mandatory if Priority of a case is High

Trigger: Case Created
Condition:

• Case Priority = High

• Automation Status is not set

Action: Prevent case creation

2. Restrict Publishing of Test Cases Without Review

Trigger: Case Updated
Condition:

• New Status = Published

• Review Status ≠ Completed (Possible custom field)

Action: Prevent update
Message: “A test case cannot be published until it has been reviewed.”

3. Prevent case transition to In Review state if Reviewer is changing from X to Y

Trigger : Case Updated. Field: Status (Any → In Review)
Condition:
Source Condition : OR/AND

• Reviewer (user custom field) is UserX

Target Condition: OR

• Reviewer (user custom field) is UserY

Action: Prevent update
Message: “Reviewer cannot change from X to Y when Review status”

3. Notify Automation Lead on Update of Automated Status from To Be Automated to In progress

Trigger: Case Updated
Condition:

• Automation Status = To Be Automated

Action: Send email
To: Automation Lead
Subject: Test Case Updated ${CASE_KEY}

4. Notify QA Lead When Automation Results Import Completes

Trigger: Automation Results Batch Completed
Condition:

• Batch Status IN (COMPLETED, ERROR, FINISHED_WITH_ERRORS)

Action: Send email
To: QA Lead

5. Only Test Leads Can Change Case Priority

Trigger: Case Updated
Condition:

• Field changed = Case Priority

• Actor NOT in group = "Test Leads"

Action: Prevent update
Message: “Only Test Leads are allowed to modify test case priority.”

6. Prevent Case Status from Moving to Deprecated for P1 cases (Published → Deprecated) by trainees

Trigger: Case Updated. Field Status changed from Published → Deprecated
Condition:

• Priority in Critical, High

• User is in group “Trainees”

Action: Prevent update
Message: “Published critical test cases cannot be moved back to Deprecated status.”

7. Only Automation Engineers Can Set Automation Status

Trigger: Case Updated. Field changed = Automation Status
Condition:

• Actor NOT in group = "Automation Engineers"

Action: Prevent update
Message: “Only Automation Engineers can update Automation Status.”

8. Block Archive of Cycles which are not closed Unless Actor Is QA Manager

Trigger: Cycle Archived
Condition:

• Cycle status is Open

• Actor NOT in group = "QA Managers"

Action: Prevent archive
Message: “This cycle is not closed. Only QA Managers can archive cycles with open status.”

9. Block Creation of Cycles if Actor is Trainee

Trigger: Cycle Created
Condition:

• Actor in group = "Trainees"

Action: Prevent creation
Message: “Only QA Managers and leads can create cycles.”

10.  Notify QA Managers if cycle created with Title containing “Regression” and Release not specified
Trigger: Cycle Created
Condition:

• Title contains = "Regression"

• Release is not set

Action: Send email
To: QA Manager
Message: “Regression cycle created without release information ${CYCLE_KEY}”

11.  Notify QA Managers if cycle is closed
Trigger: Cycle Updated. Field : Closed
Condition:

• Cycle closed status = True

Action: Send email
To: QA Manager
Message: “Cycle marked as closed : ${CYCLE_KEY}”

12.  Prevent Cycle cannot be approved if custom field like Device/Browser is not set
Trigger: Cycle Update. Field : Approval status changing from (Any → Approved)
Condition:

• Device/Browser is not Set

Action: Prevent update
Message: “Please select Browser before approval”

For further queries and suggestions, feel free to reach out to our customer support via help@aiotests.com.