Automation Rules in AXQA (Rule-Based Test Execution & Scheduling)

Automation Rules define when and how tests should run automatically. Instead of manually triggering executions, you create structured rules that instruct the system to execute specific test cases or Test Campaigns under defined conditions.

Why it matters

• Eliminates repetitive manual execution.
• Ensures important tests run consistently.
• Supports scalable regression workflows.
• Creates predictable and auditable automation behavior.

When to use it

• You want a Test Campaign to run after every new build.
• You need automated checks triggered by specific events.
• You want to enforce regular health checks.
• You need conditional execution (e.g., follow-up actions after failure).

Core concepts

• Automation Rule – A structured instruction that defines execution behavior.
• Trigger – The event or condition that starts the automation.
• Target – The test case or Test Campaign to be executed.
• Execution Mode – Determines whether it runs instantly, on schedule, or conditionally.
• Run History – A log of executions initiated by the rule.

How it works

1. You select the target (test case or Test Campaign).
2. You define the trigger type (manual automation, scheduled, or conditional).
3. The rule is saved and activated.
4. The system monitors for the trigger condition.
5. When triggered, execution starts automatically and results are recorded.

How to use it

Step 1: Define the target

Choose whether the rule applies to a single test case or a full Test Campaign.

Step 2: Choose the trigger

Select how the automation should start:

On-demand automation, Scheduled execution, Conditional trigger 

Step 3: Activate the rule

Once saved, the rule becomes active and will execute automatically when conditions are met.

Step 4: Monitor outcomes

Review automation history to verify correct behavior and detect recurring issues.

Best practices

• Keep rules focused and purposeful.
• Avoid creating overlapping rules for the same target.
• Test new rules before applying them to production environments.
• Document the intent of each rule for team clarity.

Common mistakes

❌ Creating duplicate automation rules
✔ Review existing rules before adding new ones.

❌ Activating automation without testing the workflow
✔ Validate execution logic before enabling it widely.

❌ Ignoring automation logs
✔ Regularly monitor rule performance and execution history.

Security & permissions

• Only authorized users can create or modify automation rules.
• Execution permissions are validated at run time.
• Automation respects project-level access restrictions.

Related documentation

• Automation Overview
• Execution Types
• Scheduled Automation