Glossary · Argus QA

What is test evidence?

What is test evidence? A clear explanation for Azerbaijani business — and how Argus QA applies it.

Understanding AI-Driven Test Evidence

Test evidence serves as the definitive documented proof that a software feature has been executed and verified. In traditional testing, this often consists of binary pass/fail markers; however, within the Argus QA ecosystem, evidence evolves into a comprehensive audit trail. By leveraging AI computer-use agents, the system captures a granular history of every interaction, transforming a simple test result into a detailed narrative of the agent's journey through the application. This sophisticated approach to evidence collection includes high-resolution screenshots, explicit reasoning logs, and step-by-step action histories that justify every outcome. By persisting every turn—regardless of whether the step passed or failed—Argus QA provides a transparent record that eliminates the 'black box' nature of AI. This ensures that quality assurance teams have the necessary context to distinguish between a genuine product regression and an agent-side execution error.

Capabilities

The Strategic Value of Robust Evidence

✓

Provides a transparent, immutable audit trail of every action taken during a test run for complete visibility.

✓

Accelerates root-cause analysis by classifying failures into precise categories such as product defects, environment issues, or timeouts.

✓

Ensures strict accountability by recording the environment build stamp and the identity of the user who initiated the run.

✓

Eliminates debugging guesswork by pairing visual screenshots with the agent's stated reasoning for every decision.

✓

Facilitates centralized reporting through seamless integration with external test management tools like Qase.io.

✓

Optimizes operational costs by providing metered model spend aggregated from individual calls up to the entire release suite.

How Argus QA Captures Evidence

Step-by-Step Persistence

Every action taken by the AI agent is persisted, whether it passed or failed, including the screenshot observed and the reasoning used to make the decision.

Independent Verification

To ensure objectivity, assertions are checked by an independent verifier rather than by the agent that performed the work.

Detailed Failure Classification

Failures are not generic; they are categorized as product defects, agent failures, environment failures, assertion failures, loops, step limits, or timeouts.

Ready-to-File Bug Reports

Suspected product bugs are flagged with a comprehensive report for human review, ensuring the AI never asserts a defect on its own authority.

Cost and Performance Tracking

Evidence includes metered model spend aggregated from the call level up to the entire release suite.

The Evidence Generation Process

1The agent observes a screenshot and states its reasoning before taking one action per turn.
2The system records the build stamp of the environment and the specific accounts used for each role.
3An independent verifier checks the assertions against the resulting state of the application.
4The run results, including cost and failure trends, are logged in a searchable bug register.
5Evidence is synced back to external management tools, providing a direct link from the test case to the detailed Argus evidence.

Frequently Asked Questions

Does the AI automatically file bugs in Jira or Qase?

No. To maintain accuracy and human oversight, the AI flags suspected bugs and generates a ready-to-file report, but a human must review and manually file the defect.

How does Argus handle evidence for multi-role workflows?

It utilizes independent, authenticated browser sessions for different roles (e.g., creator, approver, and supplier), recording the distinct actions and evidence for each session separately.

Is the evidence based on fixed coordinates or selectors?

No. Evidence is based on step intents and visual observations. This avoids the fragility associated with coordinates or selectors, making the evidence more resilient to UI changes.

How is the accuracy of the test results verified?

Argus employs a two-tier verification system: the AI agent performs the work, but a separate, independent verifier checks the assertions to ensure the results are objective and unbiased.

Can I track the cost associated with the evidence generated?

Yes. Every model call is metered, and costs are aggregated from the individual call level up through the step, scenario, suite, and finally the entire release.

Ready to modernize your QA evidence?

Experience autonomous regression testing with Argus QA and turn your test logs into actionable insights.

Request a demo