playwright-best-practices

name	playwright-best-practices
description	Core patterns for writing maintainable, reliable Playwright tests with TypeScript. Use when writing new tests, refactoring existing ones, or reviewing test quality. Covers test structure, selectors, waits, assertions, page objects, fixtures, and common anti-patterns.

Playwright Best Practices Skill

This skill contains comprehensive best practices for writing maintainable, reliable Playwright tests with TypeScript.

Core Principles

1. Tests should be reliable - No flaky tests
2. Tests should be fast - Parallel execution, efficient waits
3. Tests should be maintainable - Clear structure, reusable code
4. Tests should be readable - Self-documenting, clear intent
5. Tests should be isolated - No dependencies between tests

Table of Contents

• Test Structure
• Selectors
• Waits and Timing
• Assertions
• Page Objects
• Fixtures
• Test Organization
• Error Handling
• Common Anti-Patterns

---

Test Structure

✅ Good Practice

import { test, expect } from '@playwright/test';
import { LoginPage } from '../page-objects/LoginPage';

test.describe('User Authentication', () => {
  test('should login successfully with valid credentials', async ({ page }) => {
    const loginPage = new LoginPage(page);
    
    await loginPage.navigate();
    await loginPage.login('[e-mail]', 'SecurePass123');
    
    await expect(page).toHaveURL(/.*dashboard/);
    await expect(page.getByRole('heading', { name: 'Welcome' })).toBeVisible();
  });

  test('should show error message with invalid credentials', async ({ page }) => {
    const loginPage = new LoginPage(page);
    
    await loginPage.navigate();
    await loginPage.login('[e-mail]', 'WrongPassword');
    
    await expect(loginPage.errorMessage).toBeVisible();
    await expect(loginPage.errorMessage).toHaveText('Invalid credentials');
  });
});

❌ Bad Practice

// Vague test name, no page object, poor structure
test('test 1', async ({ page }) => {
  await page.goto('https://example.com/login');
  await page.waitForTimeout(2000); // Hard-coded wait
  await page.locator('#user').fill('[e-mail]'); // CSS selector
  await page.locator('#pass').type('password');
  await page.locator('button').click(); // Ambiguous selector
  await page.waitForTimeout(3000); // Another hard-coded wait
});

Why the good practice is better:

• ✅ Descriptive test names explain what's being tested
• ✅ Uses page objects for reusability
• ✅ Proper assertions verify expected outcomes
• ✅ No hard-coded waits
• ✅ Tests are grouped logically in describe blocks

---

Selectors

Priority Order (Use in this order)

1. getByRole - Accessibility-first, semantic
2. getByLabel - Form elements with labels
3. getByPlaceholder - Form elements with placeholders
4. getByText - Text content (use sparingly)
5. getByTestId - Last resort for complex elements

✅ Good Practice

// 1. Best - Role-based (accessible)
await page.getByRole('button', { name: 'Submit' }).click();
await page.getByRole('textbox', { name: 'Email' }).fill('[e-mail]');
await page.getByRole('heading', { name: 'Dashboard' }).waitFor();

// 2. Good - Label-based (forms)
await page.getByLabel('Password').fill('SecurePass123');
await page.getByLabel('Remember me').check();

// 3. Acceptable - Placeholder (when no label)
await page.getByPlaceholder('Enter your email').fill('[e-mail]');

// 4. Last resort - Test ID (for complex elements)
await page.getByTestId('prescription-card-123').click();

❌ Bad Practice

// CSS selectors - brittle, not accessible
await page.locator('#submit-btn').click();
await page.locator('.form-input[name="email"]').fill('[e-mail]');
await page.locator('div > div > button:nth-child(2)').click();

// XPath - even worse
await page.locator('//div[@class="container"]/button[1]').click();

// Ambiguous selectors
await page.locator('button').click(); // Which button?
await page.locator('input').fill('text'); // Which input?

Why the good practice is better:

• ✅ Accessible selectors work with screen readers
• ✅ Resilient to CSS/structure changes
• ✅ Self-documenting (you know what element you're targeting)
• ✅ Follows web accessibility standards

Selector Patterns

// ✅ Chaining for specificity
await page
  .getByRole('main')
  .getByRole('button', { name: 'Add to Cart' })
  .click();

// ✅ Filter for dynamic lists
await page
  .getByRole('listitem')
  .filter({ hasText: 'Prescription #123' })
  .getByRole('button', { name: 'Refill' })
  .click();

// ✅ Nth element (when necessary)
const firstPrescription = page.getByRole('article').first();
const lastPrescription = page.getByRole('article').last();
const thirdPrescription = page.getByRole('article').nth(2);

---

Waits and Timing

✅ Good Practice

// Auto-waiting (preferred) - Playwright waits automatically
await page.getByRole('button', { name: 'Submit' }).click();
await expect(page.getByText('Success')).toBeVisible();

// Explicit wait for specific conditions
await page.getByRole('progressbar').waitFor({ state: 'hidden' });
await page.getByRole('alert').waitFor({ state: 'visible', timeout: 10000 });

// Wait for network to be idle (for SPAs)
await page.waitForLoadState('networkidle');

// Wait for specific response
await page.waitForResponse(resp => 
  resp.url().includes('/api/prescriptions') && resp.status() === 200
);

❌ Bad Practice

// Hard-coded timeouts
await page.waitForTimeout(2000); // Never use this
await page.waitForTimeout(5000); // Seriously, don't

// Arbitrary waits
await page.click('button');
await new Promise(resolve => setTimeout(resolve, 3000)); // NO!

Why the good practice is better:

• ✅ Playwright has built-in auto-waiting
• ✅ Tests run as fast as possible
• ✅ No unnecessary delays
• ✅ Clear intent (waiting for what?)

---

Assertions

✅ Good Practice

// Visibility assertions
await expect(page.getByRole('heading', { name: 'Dashboard' })).toBeVisible();
await expect(page.getByRole('alert')).toBeHidden();

// Text assertions
await expect(page.getByRole('status')).toHaveText('Order confirmed');
await expect(page.getByRole('heading')).toContainText('Welcome');

// URL assertions
await expect(page).toHaveURL(/.*dashboard/);
await expect(page).toHaveURL('https://example.com/prescriptions');

// Attribute assertions
await expect(page.getByRole('button', { name: 'Submit' })).toBeEnabled();
await expect(page.getByRole('button', { name: 'Delete' })).toBeDisabled();
 (page.()).();


 (page.()).();


 (page.(, { :  })).(, );

❌ Bad Practice

// No assertions
await page.click('button');
// What happened? Did it work?

// Weak assertions
const text = await page.locator('.message').textContent();
expect(text).toBe('Success'); // Not using Playwright's assertions

// Checking existence instead of visibility
const button = await page.$('button');
expect(button).not.toBeNull(); // Element might exist but be hidden

Why the good practice is better:

• ✅ Auto-retrying assertions (handles timing issues)
• ✅ Clear, readable intent
• ✅ Better error messages
• ✅ Verifies actual user-visible behavior

---

Page Objects

✅ Good Practice

// page-objects/LoginPage.ts
import { Page, Locator } from '@playwright/test';

export class LoginPage {
  readonly page: Page;
  readonly emailInput: Locator;
  readonly passwordInput: Locator;
  readonly submitButton: Locator;
  readonly errorMessage: Locator;

  constructor(page: Page) {
    this.page = page;
    this.emailInput = page.getByLabel('Email');
    this.passwordInput = page.getByLabel('Password');
    this.submitButton = page.getByRole('button', { name: 'Sign In' });
    this.errorMessage = page.getByRole('alert');
  }

  async navigate() {
    await ..();
  }

   () {
     ..(email);
     ..(password);
     ..();
  }

   () {
     ..(email);
     ..(password);
     ..();
  }

   (): <> {
      ..() || ;
  }
}

Using the Page Object

// tests/auth/login.spec.ts
import { test, expect } from '@playwright/test';
import { LoginPage } from '../../page-objects/LoginPage';

test('successful login', async ({ page }) => {
  const loginPage = new LoginPage(page);
  
  await loginPage.navigate();
  await loginPage.login('[e-mail]', 'SecurePass123');
  
  await expect(page).toHaveURL(/.*dashboard/);
});

❌ Bad Practice

// No page object - duplicated selectors everywhere
test('login test 1', async ({ page }) => {
  await page.goto('/login');
  await page.locator('#email').fill('[e-mail]');
  await page.locator('#password').fill('pass');
  await page.locator('button').click();
});

test('login test 2', async ({ page }) => {
  await page.goto('/login');
  await page.locator('#email').fill('[e-mail]'); // Duplicated!
  await page.locator('#password').fill('pass');
  await page.locator('button').click();
});

Why the good practice is better:

• ✅ Single source of truth for selectors
• ✅ Reusable across tests
• ✅ Easy to maintain (change in one place)
• ✅ Type-safe with TypeScript
• ✅ Encapsulates page-specific logic

---

Fixtures

✅ Good Practice

// fixtures/auth.fixture.ts
import { test as base } from '@playwright/test';
import { LoginPage } from '../page-objects/LoginPage';

type AuthFixtures = {
  loginPage: LoginPage;
  authenticatedPage: Page;
};

export const test = base.extend<AuthFixtures>({
  loginPage: async ({ page }, use) => {
    const loginPage = new LoginPage(page);
    await use(loginPage);
  },

  authenticatedPage: async ({ page }, use) => {
    // Auto-login for tests that need authenticated state
    const loginPage = new LoginPage(page);
    await loginPage.navigate();
    await loginPage.login('[e-mail]', 'SecurePass123');
    await page.waitForURL(/.*dashboard/);
    await use(page);
  },
});

export { expect } from '@playwright/test';

Using Fixtures

import { test, expect } from '../fixtures/auth.fixture';

test('user can view prescriptions', async ({ authenticatedPage }) => {
  // Already logged in!
  await authenticatedPage.getByRole('link', { name: 'Prescriptions' }).click();
  await expect(authenticatedPage).toHaveURL(/.*prescriptions/);
});

Benefits:

• ✅ Shared setup/teardown logic
• ✅ Better test isolation
• ✅ Composable and reusable
• ✅ Automatic cleanup

---

Test Organization

✅ Good Practice

tests/
├── auth/
│   ├── login.spec.ts
│   ├── logout.spec.ts
│   ├── password-reset.spec.ts
│   └── registration.spec.ts
├── pharmacy/
│   ├── prescription-flow/
│   │   ├── create-prescription.spec.ts
│   │   ├── refill-prescription.spec.ts
│   │   └── cancel-prescription.spec.ts
│   └── medication-search.spec.ts
├── patient-portal/
│   ├── appointments.spec.ts
│   └── medical-records.spec.ts
└── billing/
    ├── payment-methods.spec.ts
    └── invoices.spec.ts

File Naming

• ✅ feature-name.spec.ts - Descriptive, lowercase with dashes
• ❌ test1.ts - Not descriptive
• ❌ TestLoginFeature.spec.ts - Not using kebab-case

Test Naming

// ✅ Good - Descriptive, follows pattern
test('should display error when email is invalid', async ({ page }) => {});
test('should allow user to refill prescription with one click', async ({ page }) => {});

// ❌ Bad - Not descriptive
test('test1', async ({ page }) => {});
test('it works', async ({ page }) => {});

---

Error Handling

✅ Good Practice

test('should handle network errors gracefully', async ({ page }) => {
  // Simulate network failure
  await page.route('**/api/prescriptions', route => route.abort());
  
  await page.getByRole('button', { name: 'Load Prescriptions' }).click();
  
  await expect(page.getByRole('alert')).toHaveText(
    'Unable to load prescriptions. Please try again.'
  );
});

test('should retry failed API calls', async ({ page }) => {
  let attemptCount = 0;
  
  await page.route('**/api/data', route => {
    attemptCount++;
    if (attemptCount < 3) {
      route.abort();
    } else {
      route.continue();
    }
  });
  
  // Test should succeed after retries
  await page.goto('/dashboard');
  await expect(page.getByRole('main')).toBeVisible();
});

---

Common Anti-Patterns

❌ Anti-Pattern 1: Hard-Coded Waits

await page.click('button');
await page.waitForTimeout(5000); // DON'T DO THIS

Fix: Use auto-waiting or explicit waits

await page.getByRole('button').click();
await expect(page.getByText('Success')).toBeVisible();

---

❌ Anti-Pattern 2: Brittle CSS Selectors

await page.locator('div.container > div:nth-child(3) > button').click();

Fix: Use accessible selectors

await page.getByRole('button', { name: 'Submit' }).click();

---

❌ Anti-Pattern 3: No Page Objects

// Selectors duplicated in every test
test('test1', async ({ page }) => {
  await page.locator('#email').fill('[e-mail]');
  await page.locator('#password').fill('pass');
});

test('test2', async ({ page }) => {
  await page.locator('#email').fill('[e-mail]');
  await page.locator('#password').fill('pass');
});

Fix: Create page objects

const loginPage = new LoginPage(page);
await loginPage.login('[e-mail]', 'pass');

---

❌ Anti-Pattern 4: Tests Depend on Each Other

let userId: string;

test('create user', async ({ request }) => {
  const response = await request.post('/users', { data: {...} });
  userId = (await response.json()).id; // Stored for next test
});

test('update user', async ({ request }) => {
  await request.patch(`/users/${userId}`, { data: {...} }); // Depends on previous test
});

Fix: Each test should be independent

test('update user', async ({ request }) => {
  // Create user in this test
  const createResponse = await request.post('/users', { data: {...} });
  const userId = (await createResponse.json()).id;
  
  // Now update it
  await request.patch(`/users/${userId}`, { data: {...} });
});

---

❌ Anti-Pattern 5: Testing Implementation Details

test('state is set correctly', async ({ page }) => {
  await page.evaluate(() => {
    // Checking internal state - BAD
    return window.__app__.state.isLoggedIn === true;
  });
});

Fix: Test user-visible behavior

test('user sees dashboard after login', async ({ page }) => {
  const loginPage = new LoginPage(page);
  await loginPage.login('[e-mail]', 'pass');
  
  await expect(page).toHaveURL(/.*dashboard/);
  await expect(page.getByRole('heading', { name: 'Dashboard' })).toBeVisible();
});

---

Quick Reference Checklist

Before committing a test, verify:

• Test name clearly describes what's being tested
• Uses accessible selectors (getByRole, getByLabel)
• No hard-coded waitForTimeout
• Includes proper assertions
• Uses page objects for reusable code
• Test is isolated (doesn't depend on other tests)
• Error cases are handled
• Test is in the correct folder (organized by domain)
• TypeScript types are properly defined
• Comments explain business logic (not implementation)

---

Pre-Test Completion Checklist

Before considering a test done, verify all of these (inspired by agentskills.io):

Before Writing

• Checked if page objects already exist for this flow
• Reviewed actual source code (translation keys, component structure)
• Searched for similar existing tests to avoid duplication
• Identified correct folder location based on business domain

Test Structure

• Uses Given/When/Then (Gherkin) or Arrange/Act/Assert structure
• Test name starts with "should" and describes expected behavior
• Organized in descriptive describe blocks
• Each test is independent and parallelizable

Selectors & Interactions

• Uses accessibility-first selectors (getByRole > getByLabel > getByTestId)
• No CSS class selectors or XPath
• No waitForTimeout or networkidle
• API responses awaited with page.waitForResponse where needed

Assertions & Data

• Meaningful assertions with custom error messages
• Test state set up via API calls (not UI interactions)
• All text references use actual translation keys (not hardcoded)
• Cleanup in afterEach (with try-catch to prevent test failure)

Validation

• ESLint passes: npx eslint <test-file>
• Test runs in isolation: npx playwright test <file> --repeat-each=5
• No test.only, page.pause(), or console.log left in code
• Passes on both headed and headless modes

---

Related Resources

• Selector Strategies Skill
• Code Organization Skill
• Error Handling Skill
• Debugging & Troubleshooting Skill
• Migration Patterns Skill
• Official Playwright Docs