Viewing Test Results in Donobu Studio

When you run tests with the Donobu Playwright Extension, the results are automatically synced to Donobu Studio. This page covers how Extension test results appear in Studio and the Extension-specific details you should be aware of.

For a full guide to navigating the results view, diagnosing failures, and understanding token usage, see Viewing Results in Donobu Studio. For a general introduction to Studio, see the Studio documentation.

How Extension results appear in Studio

Each Playwright test run that uses page.ai() or other Donobu methods produces one flow in Studio. These flows appear alongside any flows you've created directly in Studio, in the same flow list view.

How flow names are generated

When a flow is created by the Extension, its name is derived from the Playwright test's file name, the test.describe string, and the test string. For example:

// checkout.spec.ts

test.describe('Checkout Test', () => {
  test('user can complete checkout', async ({ page }) => {
    await page.ai('Add the first item to the cart and proceed to checkout');
  });
});

This test would appear in Studio with a flow name like checkout.spec.ts > Checkout Test > user can complete checkout, matching the file name and the strings passed to test.describe() and test().

If a single test contains multiple page.ai() calls, they will be combined into a single flow.

Cached vs. live runs from the Extension

Extension flows show the same run mode indicators as Studio-created flows:

• Autonomous — the AI made live decisions during this run (first run, or cache was invalidated)
• Deterministic — the flow replayed a cached action sequence without calling the AI

When self-healing is enabled, you may see a flow that started as Deterministic but fell back to Autonomous after the cached sequence failed. The step timeline in Studio will show exactly where the self-healing kicked in.

Finding Extension results in Studio

To locate a specific test run in Studio:

1. Open View Flows in Studio
2. Search by the test name or flow ID
3. If you have the test-flow-metadata.json artifact from CI (included in the Playwright test results), the flow ID is listed there