CtrlK
BlogDocsLog inGet started
Tessl Logo

tessl-labs/playwright-testing

Playwright E2E testing patterns — web-first assertions, user-visible locators, network interception, fixtures, authentication, and parallel execution

98

1.81x
Quality

99%

Does it follow best practices?

Impact

98%

1.81x

Average score across 5 eval scenarios

SecuritybySnyk

Passed

No known issues

Overview
Quality
Evals
Security
Files

task.mdevals/scenario-1/

E2E Tests for an Admin Dashboard

Problem/Feature Description

A SaaS app has an admin dashboard that requires login. Write Playwright E2E tests for the dashboard.

The app runs on http://localhost:3000 with these pages:

  • /login -- email + password login form with a "Sign in" button
  • /dashboard -- shows stats cards (total users, active sessions, revenue) and a users table
  • /dashboard/users -- user management page with search, invite button, and user list
  • /dashboard/settings -- app settings form with "Save" button

The app has these API endpoints:

  • POST /api/auth/login -- authenticates user (returns JWT in cookie)
  • GET /api/dashboard/stats -- returns dashboard statistics
  • GET /api/users -- returns paginated user list
  • POST /api/users/invite -- sends user invitation

All dashboard pages require authentication. Unauthenticated requests redirect to /login.

Output Specification

Produce:

  • playwright.config.ts -- Playwright configuration
  • e2e/dashboard.spec.ts -- test file for the dashboard
  • package.json -- with @playwright/test dependency listed

You may create additional files for good test organization (fixtures, page objects, auth setup).

evals

scenario-1

criteria.json

task.md

tile.json