wsbaser:verify-feature-playwright

You can run parallel E2E tests with Playwright by orchestrating up to five distinct CLI sessions concurrently. This approach streamlines QA workflows by executing multiple test tracks simultaneously, significantly reducing overall test execution time.

Generating HTML reports from Playwright CLI tests is best handled by integrating with a dedicated reporting workflow. This skill collects test evidence like screenshots and console logs, then feeds them into a reporting skill to produce shareable HTML artifacts.

Playwright browser testing supports automated screenshot collection to provide visual validation during test execution. This skill orchestrates the capture of screenshots and console logs as evidence, ensuring visual validation data is readily available for QA review.

You can run Playwright E2E tests in either headless or headed modes for QA automation. This skill supports both configurations, allowing you to execute tests in the background for CI pipelines or visually monitor browser interactions during local debugging.

To validate database state during Playwright E2E testing, you can utilize DB validation hooks within your test workflow. This skill supports integrating these hooks to verify backend data consistency alongside your frontend browser testing sessions.

The main limitation of running parallel Playwright CLI sessions is a maximum capacity of five concurrent tracks. Exceeding this limit requires queueing additional tests, which may impact overall execution time for large test suites.