Playwright E2E testing patterns — web-first assertions, user-visible locators, network interception, fixtures, authentication, and parallel execution
98
99%
Does it follow best practices?
Impact
98%
1.81xAverage score across 5 eval scenarios
Passed
No known issues
A web app has a notifications page that shows real-time updates. Write Playwright E2E tests.
The app runs on http://localhost:3000 with these pages:
/notifications -- shows a list of notifications with:
/settings/notifications -- notification preferences form with toggles for email, push, and in-app notificationsAPI endpoints:
GET /api/notifications -- returns notification listPATCH /api/notifications/:id/read -- marks single notification as readPOST /api/notifications/mark-all-read -- marks all as readGET /api/notifications/count -- returns unread countProduce:
playwright.config.ts -- Playwright configuratione2e/notifications.spec.ts -- E2E test filepackage.json -- with @playwright/test dependency listedYou may create additional files for good test organization.