Manual vs Automated Test Execution Types in AXQA

Not every test run is the same. In AXQA, executions can be triggered in different ways depending on your workflow — manually by a tester, automatically by a rule, or on a defined schedule. Choosing the right execution type keeps your testing process efficient and controlled.

Why it matters

• Provides flexibility for different testing strategies.
• Balances manual validation with automated coverage.
• Improves visibility in reports by identifying how each run was triggered.

When to use it

• You need quick manual validation during development.
• You want repeatable regression runs without manual effort.
• You require regular health checks (nightly, weekly, etc.).
• You need clear audit trails showing how a test was executed.

Core concepts

• Manual Execution – A tester starts the run directly from the platform.
• Automated Execution – The system triggers execution based on a defined rule.
• Scheduled Execution – Execution occurs at predefined time intervals.
• Execution Source – Indicates how the run was initiated.

How it works

1. A test case or Test Campaign is selected for execution.
2. The execution type determines how the run is initiated.
3. The system records the execution source along with the results.
4. All execution types follow the same validation and logging process.

How to use it

Manual Execution

Triggered directly by a tester. Best suited for exploratory testing, debugging, or ad-hoc validation.

Automated Execution

Triggered automatically by a defined automation rule. Useful for recurring regression or rule-based workflows.

Scheduled Execution

Runs at predefined times (e.g., nightly builds or weekly checks). Ideal for ongoing monitoring without manual intervention.

Best practices

• Use manual execution for unstable or newly created test cases.
• Use automation for mature, repeatable workflows.
• Use scheduling for regular regression or monitoring tasks.
• Keep execution history clear by selecting the appropriate type.

Common mistakes

❌ Scheduling unstable test cases
✔ Stabilize them first before enabling automation or scheduling.

❌ Overusing manual runs for repetitive tasks
✔ Convert repeatable flows into automated rules.

❌ Ignoring execution source in reporting
✔ Use execution type data to analyze workflow efficiency.

Security & permissions

• Execution rights are validated regardless of execution type.
• Scheduled and automated runs respect the same access rules as manual runs.
• Unauthorized execution attempts are blocked automatically.

Related documentation

• Automation Overview
• Automation Rules
• Test Campaign Overview