analyze-test-codebase

Scanning a Playwright test codebase locates configuration files, extracts settings like baseURL and projects, and identifies testing patterns. This generates a structured report detailing conventions, directory structure, and supporting infrastructure for quick decision-making.

A Playwright configuration analysis extracts baseURL, testDir, projects, use options such as viewport and headless, webServer, and globalSetup or globalTeardown settings. It verifies these core configuration fields to document the project's current testing setup.

Yes, the analysis detects common Playwright testing patterns including locator strategies, wait strategies, data management, Page Objects, auth handling, and custom fixtures. It scans the test directory to identify these patterns and understand organization strategies.

You can check for supporting infrastructure by scanning the project for fixtures, pages, environment files, CI configs, npm scripts, HARs, and snapshots. This informs test coverage and provides a complete view of the supporting test infrastructure.

The best way to summarize a Playwright test directory structure is to scan and count tests, identify naming conventions, and understand organization strategies. This produces a concise report of the test setup without modifying tests or running the live app.