Knowledge Graph

A structured map of everything an application does — all its pages, pathways, workflows, and API calls — built by systematically exploring the application rather than reading its source code. In an agentic testing context, a knowledge graph is generated automatically by an agent that navigates the running application and records what it finds. It gives teams a ground-truth picture of what has actually been built, which may differ from what was specified. It can be used to inform test strategy, surface coverage gaps, and support intent validation by comparing the graph against original requirements.

A connected representation of information that captures context and relationships, not just raw data, so tools can produce knowledge quickly and use it to test more efficiently.

So what? Data on its own is no longer enough; the context and relationships around it are what make it useful. Debate remains about how teams know what has actually been tested, though human testing has its own blind spots too.

Example: A test management tool linking tickets, tests and results so it can surface knowledge about the product, rather than holding them as separate records.