Executing Test Cases via Smart Agent in AXQA

When a test case is executed through Smart Agent, the execution happens locally — inside your network — while still being fully tracked within AXQA. The Agent retrieves assigned test cases, runs them in sequence, performs validations, and securely returns structured results to the platform.

As part of the AXQA Execution Intelligence Platform, Smart Agent enables structured, local execution within private environments while preserving centralized validation logic, execution traceability, and reporting integrity.

Why this execution mode is powerful

• Runs tests inside restricted or private environments.
• Maintains full execution history and reporting.
• Supports advanced validation logic.
• Preserves performance and security boundaries.

Execution flow

1. The tester logs into the Smart Agent application.
2. The Agent retrieves test cases assigned to that user.
3. The selected test case begins execution locally.
4. Each step runs in the defined order.
5. Validations are performed.
6. Results and execution metadata are sent back to AXQA.

What happens during step execution

• Action steps are executed locally against the target system.
• Expected validations are evaluated.
• Status is determined per step.
• Execution time and response details are recorded.

Handling advanced scenarios

Repeated execution for list-based inputs

If a request contains a list of values, the Agent automatically executes the test multiple times — once per value — and records all responses.

Expected-only validations

If a step defines only a validation scenario, the Agent executes the validation accordingly without requiring a separate action step.

Mixed execution types

Manual and automated logic can coexist within the same test case, and the Agent processes each step according to its definition.

Metadata captured

• Execution source (Smart Agent).
• Status code and validation outcome.
• Execution duration.
• Response size.
• Timestamp and build reference.

How results are returned

• Results are securely transmitted back to AXQA.
• Each step’s outcome is stored in execution history.
• The overall test case result is calculated.
• The execution becomes part of the permanent project record.

Consistency with server execution

Smart Agent execution follows the same structured validation and reporting model as server execution. The only difference is where the execution physically takes place.

Best practices

• Ensure the Agent runs on a stable and controlled machine.
• Verify connectivity before triggering large test runs.
• Monitor execution logs for network-specific issues.
• Use Agent execution for internal systems and restricted environments.

Common mistakes

❌ Running Agent execution on an unstable network connection
✔ Use a reliable internal connection for consistent results.

❌ Mixing unrelated environments within the same Agent instance
✔ Use dedicated Agents for distinct environments when needed.

Related documentation

• Smart Agent Overview
• Internal Network Testing (High-Security Mode)
• Smart Agent Security Model
• Compare Executions