Individual green checkmarks are reassuring. A suite you can run all at once, repeatably, is what makes an API trustworthy.
Run the Whole Suite with the Collection Runner
The Collection Runner executes every request in order, runs every test, and gives you one pass/fail summary. This is where your assertions stop being decoration and become a regression safety net — the same run a CI pipeline automates later.
In Agent Mode, run a prompt like:
Run my entire Movies API collection with the Collection Runner and summarize the results: how many tests passed, how many failed, and which requests the failures came from.
Expect some red — the negative and write-path tests reflect ideal behavior the sandbox doesn't implement. For each failure, decide whether it's a bug in the API or a test asserting behavior this API never promised, and note which.
See it for yourself: In the run results, click any request to open its response and Test Results and see exactly which assertions passed or failed — not just the totals.
Let Agent Mode Report on Coverage
The last skill of a good tester is knowing what they haven't tested. Agent Mode can read your whole collection and surface the gaps — an endpoint with no assertions, an error path never exercised. Using AI to audit your own suite closes the loop.
In Agent Mode, run a prompt like:
Review the tests across my Movies API collection and give me a coverage summary: which requests have assertions, what kinds of checks each has (status, schema, value, negative, performance), and which meaningful cases are still untested. Suggest the three most valuable tests to add next.
Treat the suggestions as a checklist to reason about, not a to-do list to run blindly. For each proposed test, ask what it would protect against — if you can answer, add it.