Automation & Smart Agent

Smart Agent Test Automation in AXQA (Hybrid Execution Model)

Automation in AXQA can run directly from the platform or through a Smart Agent installed on a local machine. This flexibility allows teams to execute tests in different environments — whether server-side APIs or client-side applications that require local access.

Why it matters

Supports both backend and local environment testing.
Enables automation for systems that cannot be accessed from the cloud.
Provides greater control over execution environments.
Extends automation beyond standard API-based workflows.

When to use it

You need to run tests against local builds or internal networks.
You’re testing environments that require device-level access.
You want distributed execution across multiple machines.
You need higher execution control for specific environments.

Core concepts

Server Execution – Automation runs directly from the AXQA platform.
Smart Agent – A local application that executes tests on a connected machine.
Execution Source – Indicates whether the run was triggered via server or agent.
Secure Communication – The agent connects securely to receive and report execution results.

How it works

An automation rule is triggered.
The execution target is identified (server or Smart Agent).
If server-based, the platform runs the tests directly.
If agent-based, the Smart Agent receives the instruction and executes locally.
Results are returned and recorded in the platform.

Note

Execution source is handled per test case. If the first test case runs on the server and the second runs via Smart Agent, the system follows each test case’s individual configuration without conflict. Execution is performed according to the settings defined inside the test case itself and the assigned responsible entity.

Warning

Manual test cases are automatically skipped during automation runs, as they require human interaction and are not eligible for automated execution.

How to use it

Step 1: Choose execution environment

When configuring automation, decide whether execution should happen on the server or through a Smart Agent.

Step 2: Ensure Smart Agent is active

If using agent-based execution, confirm the agent is installed, running, and connected.

Step 3: Configure automation rule

Create or update the rule to use the selected execution environment.

Step 4: Monitor results

Execution history will show where the test ran and its outcome.

Best practices

Use server execution for standard API validations.
Use Smart Agent for local builds or restricted environments.
Keep agent machines stable and dedicated to testing tasks.
Monitor connectivity to avoid missed executions.

Common mistakes

❌ Running local-only tests on the server
✔ Select Smart Agent when environment access is required.

❌ Leaving the Smart Agent offline
✔ Verify agent connectivity before relying on automation.

❌ Not distinguishing execution sources in reporting
✔ Use execution source data to analyze environment-specific issues.

Security & permissions

Agent communication is secured and authenticated.
Execution permissions are validated before any instruction is sent.
Agent-based execution follows the same access controls as server execution.

AXQA

Did You Know?