For the complete documentation index, see llms.txt. This page is also available as Markdown.

Application Knowledge

What TestDrive has learned about your application, how facts get validated, and how to correct them

Every run records what it discovered about your application, and the workspace keeps it. That's what makes the tenth run faster and more accurate than the first: the agent isn't rediscovering where the login form is, it already knows.

The Knowledge tab is that record. On a new workspace it says "Nothing learned yet. Runs record what they discover about the app here."

What Gets Learned

Kind
Examples

Route

The pages that exist and how you reach them

Flow

Multi-step paths — sign-up, checkout, inviting a teammate

Auth

How this application is signed into

Element

The controls that matter, and how to find them reliably

Behavior

How the app responds — what it validates, what it redirects, what it caches

Flaky

The parts that aren't reliable, so a test doesn't keep blaming your product for them

How a Fact Becomes Trusted

A thing observed once might be a coincidence. TestDrive tracks how confident it is in each fact.

State
Meaning

Candidate

Observed, but not yet corroborated

Validated

Confirmed by evidence from more than one run

Conflicted

Later runs contradicted it

Rejected

Ruled out

A candidate is promoted to validated automatically once evidence for it has come from at least two distinct runs. You can also mark a fact verified by hand, which validates it immediately — useful when you know something the agent has only seen once.

Only validated knowledge is used during a run. A candidate fact is visible to you and available for review, but it can't quietly steer a test or a script build. That's the difference between a system that learns and one that accumulates mistakes.

Correcting What It Learned

Open any fact and edit it. The panel is explicit about the weight of this: corrections become the source of truth for future QA agents.

Correcting knowledge is often the fastest fix for a test that keeps going wrong in the same way — the agent isn't confused about the test, it's confident about something untrue.

Knowledge on a Run

Each run's Knowledge graph tab shows the concepts it used and the concepts it learned, which is the clearest picture of why a run behaved the way it did.

You can also download the workspace's knowledge as a bundle from the Knowledge tab toolbar.

Next Steps

Goal
Documentation

See knowledge in context of a run

Read or write knowledge from an agent

Improve the tests that produced it

Last updated

Was this helpful?