FAQ

When is a test considered resolved?

A test result is resolved when a user either links a defect to it or marks it as muted. Both actions indicate that the failure has been analyzed: defect means the failure is a known issue, muted means the failure is intentionally ignored.

What are retries?

A retry occurs when the same test runs more than once within a single launch. TestOps identifies retries by matching the test ID and environment across results in the same launch.

Retries appear in two places: on the launch overview page in the Retries section, and inside the launch on the test results page under the Retries tab of an individual result.

If the environment parameters change between runs, TestOps treats the result as a new test result rather than a retry.

Why are some test case changes not in the change log?

The change log tracks field-level edits to a test case but does not record changes to:

• relations,
• mutes,
• links,
• scenario steps,
• attachments,
• parameters.

Can I use AQL functions in widgets?

No. Functions such as now(), dayStartUtc(), weekAgo(), and currentUser() are not supported in widget queries. Use static values or date picker controls instead.

See: AQL

How to prevent test case creation when running tests on non-main branches

Configure a documentation generation policy in the project's Launches settings. The policy uses AQL to control when automated results are allowed to create or update test cases. You can filter by launch name, launch tags, or environment data to restrict test case creation to specific branches or environments.

For example, to create and update test cases only when the branch is main:

ev["Branch"]="main"

Cleanup rules are set but the database size is not decreasing

Cleanup rules remove scenario data and artifact links, but the freed space is not reclaimed immediately. PostgreSQL requires additional maintenance operations to physically reclaim space and keep query performance healthy:

• VACUUM marks deleted rows as reclaimable. Run a full VACUUM periodically and configure autovacuum for tables that see frequent deletes.
• ANALYZE updates the query planner statistics. Run it after large deletes so the planner can generate efficient execution plans.
• REINDEX rebuilds bloated indexes. After deleting large amounts of data, indexes can retain dead pages that slow down queries; REINDEX compacts them.

In addition, traces and error messages are not removed by cleanup rules. They are treated as metadata and kept even after all other artifacts are deleted. To limit their size, shorten long traces and messages before writing them to test results, or store them as attachments instead.

See: Storage maintenance

What happens when the license expires?

All user accounts switch to read-only mode and all integrations stop working. To restore access, log in as an administrator and enter a new license when prompted.

If the license has not yet expired, you can update it under Administration → License → Manage licenses.

How to check the Allure TestOps version and instance status

The version number is displayed in the user menu: click your avatar in the upper-right corner.

For a machine-readable status check, open <your-instance-url>/status in a browser or via HTTP. The endpoint returns the application status without requiring authentication.