Phoenix Playwright Tests logo

Phoenix Playwright Tests

OrganizationPopular
Arize-ai
phoenix-playwright-tests

Write Playwright E2E tests for the Phoenix AI observability platform. Use when creating, updating, or debugging Playwright tests, or when the user asks about testing UI features, writing E2E tests, or automating browser interactions for Phoenix.

Overview

PublisherArize-ai
Repositoryphoenix
Skill namephoenix-playwright-tests
Stars
11.8K
Forks
1.2K
Bundled files
2
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 2 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by Arize-ai on GitHub. Read the source before you install it.

Installation

Install the Phoenix Playwright Tests AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/Arize-ai/phoenix/tree/main/.agents/skills/phoenix-playwright-tests
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/Arize-ai/phoenix.git /tmp/phoenix
mkdir -p .claude/skills
cp -r /tmp/phoenix/.agents/skills/phoenix-playwright-tests .claude/skills/phoenix-playwright-tests
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Phoenix Playwright Tests in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Phoenix Playwright Tests on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Phoenix Playwright Tests is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Phoenix Playwright Test Writing

Write end-to-end tests for Phoenix using Playwright. Tests live in js/app/tests/ and follow established patterns.

Timeout Policy

  • Do not pass timeout args in test code under js/app/tests.
  • Tune timing centrally in js/app/playwright.config.ts (global timeout, expect.timeout, use.navigationTimeout, and webServer.timeout).

Quick Start

typescript
import { expect, test } from "@playwright/test";
import { randomUUID } from "crypto";

test.describe("Feature Name", () => {
  test.beforeEach(async ({ page }) => {
    await page.goto(`/login`);
    await page.getByLabel("Email").fill("admin@localhost");
    await page.getByLabel("Password").fill("admin123");
    await page.getByRole("button", { name: "Log In", exact: true }).click();
    await page.waitForURL("**/projects");
  });

  test("can do something", async ({ page }) => {
    // Test implementation
  });
});

Test Credentials

UserEmailPasswordRole
Adminadmin@localhostadmin123admin
Membermember@localhost.commember123member
Viewerviewer@localhost.comviewer123viewer

Selector Patterns (Priority Order)

  1. Role selectors (most robust):

    typescript
    page.getByRole("button", { name: "Save" });
    page.getByRole("link", { name: "Datasets" });
    page.getByRole("tab", { name: /Evaluators/i });
    page.getByRole("menuitem", { name: "Edit" });
    page.getByRole("cell", { name: "my-item" });
    page.getByRole("heading", { name: "Title" });
    page.getByRole("dialog");
    page.getByRole("textbox", { name: "Name" });
    page.getByRole("combobox", { name: /mapping/i });
  2. Label selectors:

    typescript
    page.getByLabel("Email");
    page.getByLabel("Dataset Name");
    page.getByLabel("Description");
  3. Text selectors:

    typescript
    page.getByText("No evaluators added");
    page.getByPlaceholder("Search...");
  4. Test IDs (when available):

    typescript
    page.getByTestId("create-dataset-button");
    // element with state — select the stable id, filter on the data attribute
    page.locator('[data-testid="llm-evaluator-form-submit-button"][data-mode="create"]');

    data-testids are scoped, fully spelled out (...-button, never ...-btn), and constant regardless of state — state is exposed via a sibling data-* attribute (data-mode, data-state, …), so never key a getByTestId off a value that only exists in one mode. If you need a data-testid that doesn't exist yet, add it following references/test-ids.md in the phoenix-frontend skill (pattern: <scope>-<subject>-<role>).

  5. CSS locators (last resort):

    typescript
    page.locator('button:has-text("Save")');

Common UI Patterns

Dropdown Menus

typescript
// Click button to open dropdown
await page.getByRole("button", { name: "New Dataset" }).click();
// Select menu item
await page.getByRole("menuitem", { name: "New Dataset" }).click();

Nested Menus (Submenus)

typescript
// Open menu, hover over submenu trigger, click submenu item
await page.getByRole("button", { name: "Add evaluator" }).click();
await page
  .getByRole("menuitem", { name: "Use LLM evaluator template" })
  .hover();
await page.getByRole("menuitem", { name: /correctness/i }).click();

// IMPORTANT: Always use getByRole("menuitem") for submenu items, not getByText()
// Playwright's auto-waiting handles the submenu appearance timing
// ❌ BAD - flaky in CI:
// await page.getByText("ExactMatch").first().click();
// ✅ GOOD - reliable:
// await page.getByRole("menuitem", { name: /ExactMatch/i }).click();

Dialogs/Modals

typescript
// Wait for dialog
await expect(page.getByRole("dialog")).toBeVisible();
// Fill form in dialog
await page.getByLabel("Name").fill("test-name");
// Submit
await page.getByRole("button", { name: "Create" }).click();
// Wait for close
await expect(page.getByRole("dialog")).not.toBeVisible();

Tables with Row Actions

typescript
// Find row by cell content
const row = page.getByRole("row").filter({
  has: page.getByRole("cell", { name: "item-name" }),
});
// Click action button in row (usually last button)
await row.getByRole("button").last().click();
// Select action from menu
await page.getByRole("menuitem", { name: "Edit" }).click();

Tabs

typescript
await page.getByRole("tab", { name: /Evaluators/i }).click();
await page.waitForURL("**/evaluators");
await expect(page.getByRole("tab", { name: /Evaluators/i })).toHaveAttribute(
  "aria-selected",
  "true",
);

Form Inputs in Sections

typescript
// When multiple textboxes exist, scope to section
const systemSection = page.locator('button:has-text("System")');
const systemTextbox = systemSection
  .locator("..")
  .locator("..")
  .getByRole("textbox");
await systemTextbox.fill("content");

Serial Tests (Shared State)

Use test.describe.serial when tests depend on each other:

typescript
test.describe.serial("Workflow", () => {
  const itemName = `item-${randomUUID()}`;

  test("step 1: create item", async ({ page }) => {
    // Creates itemName
  });

  test("step 2: edit item", async ({ page }) => {
    // Uses itemName from previous test
  });

  test("step 3: verify edits", async ({ page }) => {
    // Verifies itemName was edited
  });
});

Assertions

typescript
// Visibility
await expect(element).toBeVisible();
await expect(element).not.toBeVisible();

// Text content
await expect(element).toHaveText("expected");
await expect(element).toContainText("partial");

// Attributes
await expect(element).toHaveAttribute("aria-selected", "true");

// Input values
await expect(input).toHaveValue("expected value");

// URL
await page.waitForURL("**/datasets/**/examples");

Navigation Patterns

typescript
// Direct navigation
await page.goto("/datasets");
await page.waitForURL("**/datasets");

// Click navigation
await page.getByRole("link", { name: "Datasets" }).click();
await page.waitForURL("**/datasets");

// Extract ID from URL
const url = page.url();
const match = url.match(/datasets\/([^/]+)/);
const datasetId = match ? match[1] : "";

// Navigate with query params
await page.goto(`/playground?datasetId=${datasetId}`);

Running Tests

Before running Playwright tests, build the app so E2E runs against the latest frontend changes:

bash
pnpm run build
bash
# Run specific test file
pnpm exec playwright test tests/server-evaluators.spec.ts --project=chromium

# Run with UI mode
pnpm exec playwright test --ui

# Run specific test by name
pnpm exec playwright test -g "can create"

# Debug mode
pnpm exec playwright test --debug

Avoiding Interactive Report Server

By default, Playwright serves an HTML report after tests finish and waits for Ctrl+C, which can cause command timeouts. Use these options to avoid this:

bash
# Use list reporter (no interactive server)
pnpm exec playwright test tests/example.spec.ts --project=chromium --reporter=list

# Use dot reporter for minimal output
pnpm exec playwright test tests/example.spec.ts --project=chromium --reporter=dot

# Set CI mode to disable interactive features
CI=1 pnpm exec playwright test tests/example.spec.ts --project=chromium

Recommended for automation: Always use --reporter=list or CI=1 when running tests programmatically to ensure the command exits cleanly after tests complete.

Phoenix-Specific Pages

PageURL PatternKey Elements
Datasets/datasetsTable, "New Dataset" button
Dataset Detail/datasets/{id}/examplesTabs (Experiments, Examples, Evaluators, Versions)
Dataset Evaluators/datasets/{id}/evaluators"Add evaluator" button, evaluators table
Playground/playgroundPrompts section, Experiment section
Playground + Dataset/playground?datasetId={id}Dataset selector, Evaluators button
Prompts/prompts"New Prompt" button, prompts table
Settings/settings/general"Add User" button, users table

UI Exploration

When selectors are unclear, use the available browser tooling to explore the Phoenix UI at http://localhost:6006/datasets. Inspect accessible roles and names, interact with the target elements, and inspect the page again after navigation or DOM changes.

Use the observed roles and names to choose Playwright selectors:

UI elementPlaywright selector
Button "Save"page.getByRole("button", { name: "Save" })
Link "Datasets"page.getByRole("link", { name: "Datasets" })
Textbox "Name"page.getByRole("textbox", { name: "Name" })
Menu item "Edit"page.getByRole("menuitem", { name: "Edit" })
Tab "Evaluators 0"page.getByRole("tab", { name: /Evaluators/i })

File Naming

  • Feature tests: {feature-name}.spec.ts
  • Access control: {role}-access.spec.ts
  • Rate limiting: {feature}.rate-limit.spec.ts (runs last)

Common Gotchas

  1. Dialog not closing: Wait for a deterministic post-action signal (e.g., dialog hidden + success row visible)
  2. Multiple elements: Use .first(), .last(), or .nth(n)
  3. Dynamic content: Use regex in name: { name: /pattern/i }
  4. Flaky waits: Prefer waitForURL over waitForTimeout
  5. Menu not appearing: Wait for specific menu state/element visibility

Debugging Flaky Tests

Critical Lessons Learned

  1. Don't assume parallelism is the problem

    • Phoenix tests run with 7 parallel workers without issues
    • The app handles concurrent logins, database operations, and session management properly
    • If tests fail with parallelism, it's usually a test timing issue, not infrastructure
    • Playwright's browser context isolation is robust - each worker gets isolated cookies/sessions
  2. waitForTimeout is almost always wrong

    • page.waitForTimeout() is the #1 cause of flakiness in Phoenix tests
    • Arbitrary timeouts race against rendering and network speed
    • Always replace with state-based waits:
      typescript
      // ❌ BAD - flaky, races against rendering
      await page.waitForTimeout(500);
      await element.click();
      
      // ✅ GOOD - waits for actual state
      await element.waitFor({ state: "visible" });
      await element.click();
  3. Test the actual failure before fixing

    • Run tests with parallelism enabled to see what actually fails
    • Check error messages - they often point to the real issue
    • Don't optimize prematurely (e.g., caching auth state) if it's not the problem
  4. Phoenix test infrastructure is solid

    • In-memory SQLite works fine with parallel tests
    • No need for per-worker databases
    • No need for auth state caching
    • Tests use randomUUID() for data isolation - this works well

Debugging Workflow

When tests are flaky:

  1. Run with parallelism multiple times to catch intermittent failures:

    bash
    for i in 1 2 3 4 5; do
      pnpm exec playwright test --project=chromium --reporter=dot
    done
  2. Look for waitForTimeout usage - replace with proper waits:

    bash
    grep -r "waitForTimeout" js/app/tests/
  3. Check for race conditions in element interactions:

    • Wait for element visibility before interacting
    • Wait for network idle when needed: page.waitForLoadState("networkidle")
    • Use waitForURL after navigation actions
  4. Verify selectors are stable:

    • Avoid CSS selectors that depend on DOM structure
    • Use role/label selectors that match ARIA attributes
    • Test selectors don't break when UI updates
  5. Run with trace on failure to see what happened:

    bash
    pnpm exec playwright test --trace on-first-retry

Common Flaky Patterns and Fixes

Flaky PatternRoot CauseFix
Submenu item not foundUsing getByText() instead of getByRole()Use getByRole("menuitem", { name: /pattern/i }) for submenu items
Menu click failsMenu not fully renderedawait menu.waitFor({ state: "visible" }) before click
Dialog assertion failsDialog animation not completeAssert specific completion signal (hidden dialog + next-state element)
Navigation timeoutPage still loadingRemove waitForLoadState("networkidle") - it's flaky in CI
Element not foundDynamic content loadingWait for element visibility, not arbitrary timeout
Stale elementRe-render between locate and clickStore locator, not element handle

Test Stability Best Practices

  1. Use proper waits:

    typescript
    // Wait for element state
    await element.waitFor({ state: "visible" | "hidden" | "attached" })
    
    // Wait for network
    await page.waitForLoadState("networkidle" | "domcontentloaded" | "load")
    
    // Wait for URL change
    await page.waitForURL("**/expected-path")
  2. Use unique test data:

    typescript
    const uniqueName = `test-${randomUUID()}`;
  3. Prefer role selectors - they're less brittle:

    typescript
    page.getByRole("button", { name: "Save" }) // ✅ Good
    page.locator('button.save-btn') // ❌ Brittle
  4. Don't fight animations - wait for them:

    typescript
    await expect(dialog).not.toBeVisible();
  5. Verify URL changes after navigation:

    typescript
    await page.waitForURL("**/datasets");

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Phoenix Playwright Tests AI skill do?

Write Playwright E2E tests for the Phoenix AI observability platform. Use when creating, updating, or debugging Playwright tests, or when the user asks about testing UI features, writing E2E tests, or automating browser interactions for Phoenix.

Why use Phoenix Playwright Tests on TypingMind?

Because you install it once and use it with any model. Phoenix Playwright Tests is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Phoenix Playwright Tests in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/Arize-ai/phoenix/tree/main/.agents/skills/phoenix-playwright-tests. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Phoenix Playwright Tests?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Phoenix Playwright Tests?

As many as you like. As long as a model supports skills, you can use Phoenix Playwright Tests with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Phoenix Playwright Tests AI skill free?

It is published on GitHub by Arize-ai. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇