FAQs
Guides for authoring, running and analysing tests across web automation, API and performance — plus setup, collaboration and release notes.
Execution/result FAQs
Common questions about running tests, run statuses, results, and the differences between Local and Cloud execution.
What's the difference between Local Agent and Cloud execution?
Local runs execute on your machine via the Local Agent and are not saved. Cloud runs execute on the platform and are stored in Test Results with status, tag, release, and step-level detail.
When should I use Local vs Cloud runs?
Use Local while authoring and debugging testcases (fast, live feedback). Use Cloud for real runs you want saved for future use.
Are my Local Agent runs saved anywhere?
No. Local execution shows live step status during the run, but results are not stored. Use Cloud execution when you need saved history.
Why do I need a run tag and a Test Run Config for a cloud run?
Cloud runs require a tag (to identify/track the run) and a Test Run Config (the execution environment/settings). A combined performance API + Web run needs both a Web and an API config.
I started a run but no result appears — where is it?
Confirm you're in the correct project context, then refresh Test Results — the entry should appear with its current status. (Local runs never appear here.)
What do the run statuses mean?
QUEUED (accepted, waiting) → IN_PROGRESS (running) → PASSED/FAILED once it finishes. Other end states: ABORTED (stopped/over limits), CANCELLED (cancelled while queued), INTERRUPTED (infrastructure interruption). STOPPING is the transient state while a stop is applied.
Why is my run stuck on QUEUED?
Cloud capacity or licenses are busy, or the requested Virtual Users exceed your plan limit. Wait for resources to free up, or reduce the load.
Why did my run stop early or end as ABORTED?
It was stopped, or it exceeded the maximum execution time/limits for your plan. Shorten the load model or duration, or upgrade your plan, then re-run.
Where do I see why a step failed in web?
Open the Bug Report for the result — the bug icon opens the "Steps To Reproduce" view, which lists the failing step(s) with their Actual vs. Expected results. You can also see the reason in the result's Message tab.
One step failed and the rest show NOT_EXECUTED — why?
Web execution is fail-fast: when a step fails, the run stops and remaining steps are marked NOT_EXECUTED (they didn't run). Fix the first failing step and re-run.
What is the Bug Report / "Steps To Reproduce", and when does it show?
For a Web result that has at least one failed step, a bug icon opens a "Bug Report – Steps To Reproduce" view listing the steps with Actual vs. Expected results to help reproduce the failure.
Why are there no screenshots in my result?
Screenshots are captured only by cloud execution, according to the run config's Screenshot Capture mode. Local-agent runs don't capture screenshots, and failure-only modes attach them just to failed steps.
Can I run more than one local test at the same time?
No. The Local Agent runs one test (or recording) at a time; new requests are refused until the current one finishes. Use Cloud runs for concurrency.
Why doesn't Stop / Cancel take effect immediately?
Both are graceful — the run shows "will be stopped/cancelled soon" and passes through STOPPING before its final state. Allow it to wind down rather than re-issuing the action.
Why isn't my Test Run Config in the list when I start a run?
Run configs are scoped to an automation type (Web/API/Performance) and project. A config created for one type/project won't appear for another — create it under the matching type and project.