View API Tests

After you merge a generation PR, your tests appear on the API Tests page. This is where you review everything the agent has built, grouped by API surface.

---

​

Three numbers to know

At the top of the page, three tiles summarize your suite:

---

​

Suites, cases, and steps

Click a suite to expand its test cases. Each test case shows four things, so you can understand what it does without reading the code:

• Journey: a plain-language description of the end-to-end flow.
• Payloads: the request bodies the test sends.
• Assertions: what the test verifies.
• Steps: the individual API calls, in order. Each step shows its HTTP method, the path, and a short intent describing what the call does.

A small status marker tells you the state of each case: an active case is ready to run, while a skipped case is flagged with a Skipped chip and the reason it was set aside. A case that the agent hasn’t written code for yet shows a Pending Generation chip.

---

​

View the code

When you want the full detail, click View Code on a case to see the test source directly, with every assertion and call exactly as it runs.

---

​

Potential tests

At the bottom of the page, the Potential tests section collects cases that were skipped: “these tests were skipped because the heal agent couldn’t make them pass. Each one is either a real product bug or a test that needs to be updated.” Expand it to see each skipped case with its reason, so nothing the agent attempted is lost. These same items also surface on the Triage board for you to resolve.

---

​

Next Steps

• Set environment variables for your tests
• Archive tests you no longer need
• Run API tests