Search Results

Before we can continue, it’s important for you to learn about the basic functionality from this section to have a better understanding of how to use it, and most of all, how to debug it. These are the basic functionality available from AIQ Live Controller. ...

Review Live Reports During Execution Live Reports provide a current view of a running test. Use them to monitor health during execution, but wait for the test to complete before making final performance conclusions. Useful signals Active users and ramp behavio...

Control Test Execution Use Test Controller execution controls to start, monitor, and stop AIQ test runs. Confirm the execution plan, environment, data, and test-node capacity before starting a load or scenario execution. Before starting Verify the target envir...

Review Execution Output Execution Output provides run-level details, errors, and evidence collected during a test. Use it to understand whether a failure came from the scenario, test data, environment, or application under test. What to review Error messages a...

Review Test Case Executions Use Test Case Executions to review the result of individual scenarios within a run. This view helps identify which scenarios passed, failed, or require maintenance after execution. Use this view to Find the failed scenario or step t...

Monitor Test Nodes Test Nodes provide execution capacity for AIQ runs. Monitor them before and during execution to confirm that the planned load can run reliably. What to check The required Test Nodes are online and assigned to the correct environment. CPU, me...

Monitor Active Virtual Users Active virtual users show the number of users currently executing during a test run. Use this view to confirm that load is ramping as expected and that execution capacity matches the test design. What to check The active user count...

This section provides the current execution results so you can add custom assertions to your scenario. Several assertion types are available from the Assert Type drop-down menu, and some are exclusively for requests. For most assertions, the AIQ UI provides cu...

Use AutoCorrelation in Test Controller AutoCorrelation helps identify dynamic values that must be captured and reused for a performance test to replay correctly. Use it during script validation before increasing load. When to review correlation Requests fail a...

Contents Determining the Length of Tests Finding and Solving the Failures Evaluate Applications Ability to Achieve Linear Scalability About Reports Live Results While a Test Runs Determine if the Test System is a Performance Bottleneck Viewing Results from a P...

Determine the Right Test Duration Choose test duration based on the performance question being answered. A short smoke run can validate a script, while a longer run may be needed to observe steady-state behavior, resource growth, or reliability under sustained...

Find and Resolve Test Failures Start failure analysis with the first meaningful failure in the execution. Later errors often come from the same root cause and can distract from the actual problem. Failure triage Scenario or locator issue: the application chang...

Evaluate Linear Scalability Linear scalability compares how the application responds as load increases. A scalable system should increase throughput predictably while keeping response times and errors within acceptable limits. What to compare Virtual users or ...

Last reviewed: September 22, 2026 Use AIQ reports to evaluate execution health, response timing, failures, throughput, and supporting evidence after a test run. Recommended guidance Review reports after the run is complete for final analysis. Use live views fo...

Review Live Results While a Test Runs Use live results to monitor a test while it is running. Live data helps detect invalid runs early, but final analysis should use completed results after the run has ended and all data has been processed. Monitor during exe...

AIQ is a distributed test environment where tests run remotely on TestNodes. A TestNode is software running on a server that uses threads to operate multiple virtual users concurrently. As the number of concurrent virtual users increases, the TestNode consumes...

View Results from a Previous Test Run Use previous test run results to compare baselines, investigate past failures, and track performance trends over time. Confirm that the compared runs used the same environment, scenario version, data assumptions, and load ...

Recommended guidance Results analysis can be misleading when test data, environment, load model, monitoring, or reporting context is incomplete. Review failures and performance results with enough evidence to separate application defects from test or environme...