See who tested what

Use Traceability to see what was tested, by whom and when, and how much of a project is covered.

In short

Every run records who sent it, what was sent, what came back and when. Traceability turns that into an answer to "what was tested, by whom and when", with a coverage ring for each project. Every save of a request also keeps a revision.

Before you start

• Who: anyone who can open the project. Traceability lists tested requests only.
• Plan: Traceability is part of the paid plans.
• First: run the requests you want to see.

Steps

1. Open "Test" and choose "Coverage", then choose everyone or one team member.
2. Optionally choose a project and other filters. "Views" keeps the filters you use often under a name, to open again or share with your team.
3. Expand a project and test group to see its requests and runs.
4. Open a run to see its automatic evidence and attachments.

Result: the runs that prove testing happened, with who ran them.

What is recorded automatically

• The method and URL sent, and the request and response information kept for the run.
• Status code, duration, response size, error, date and tester.
• The saved request, test group, project and source link connected to the run.

The coverage rail

The ring is the share of saved requests run at least once in the window. Passing and failing both count as covered, so it shows whether testing happened, not whether it passed. "By project" shows tested requests out of the total, and "Who is testing" shows runs per tester.

Good to know

• Only tested requests appear in traceability. An untested request is visible on its board but is not proof that testing happened.
• Every save keeps a revision: the field, the value before and after, who changed it and when. Open a request's history and choose "Changes"; revisions cannot be edited.
• "Ask AI" can answer which endpoints a person tested, how many runs failed, or which endpoints nobody tested. The per-person breakdown holds the 60 busiest person and endpoint pairs, and the assistant says when it is partial.
• A name shows as anonymous (not signed in), (deleted user) or (not recorded) for runs without an account, from a deleted account, or from before runs recorded who sent them.
• Traceability comes with plans that include it.

If something goes wrong

• A request is missing: it has never been run.
• The coverage looks too high: failing runs count as covered. Read the pass rate in Insights.

Related

• /help/api-testing/evidence-and-reports
• /help/api-testing/insights
• /help/api-testing/captured-content