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-5/

E2E Tests for a User Registration Form

Problem/Feature Description

A web app has a user registration page. Write Playwright E2E tests for it.

The app runs on http://localhost:3000 with this page:

  • /register -- registration form with fields:
    • Full name (required)
    • Email address (required, must be valid email)
    • Password (required, minimum 8 characters)
    • Confirm password (must match password)
    • "I agree to the terms" checkbox
    • "Create Account" button
  • On success, redirects to /welcome with a welcome message
  • On failure (e.g., email already exists), shows an error banner

API endpoint:

  • POST /api/auth/register -- creates account (returns 201 on success, 409 if email exists, 400 for validation errors)

Output Specification

Produce:

  • playwright.config.ts -- Playwright configuration
  • e2e/registration.spec.ts -- E2E test file
  • package.json -- with @playwright/test dependency listed

You may create additional files for good test organization.

evals

tile.json