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

Automation Rules define when and how tests should run automatically. Instead of repeatedly triggering executions manually, you can configure specific test cases or Test Campaigns to run according to a defined schedule.

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 automatically at scheduled times.
• You need recurring regression or validation executions.
• You want to run regular health checks.
• You want to reduce repetitive manual execution.

Core concepts

• Automation Rule – A structured instruction that defines execution behavior.
• Schedule – Defines when the automated execution should run.
• Target – The test case or Test Campaign to be executed.
• Execution Mode – Defines how the scheduled execution is performed.
• 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 execution schedule.
3. The automation rule is saved and activated.
4. AXQA starts the execution at the configured time.
5. Execution results are recorded for review and history.

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: Define the schedule

Configure when the automated execution should run.

Step 3: Activate the rule

Once saved and activated, the rule executes automatically according to the configured schedule.

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