The-DevOps-Daily/devops-daily

feat: Add E2E tests with Playwright

Open

#527 opened on Dec 2, 2025

View on GitHub
 (0 comments) (0 reactions) (0 assignees)TypeScript (392 forks)github user discovery
enhancementgood first issuehacktoberfest

Repository metrics

Stars
 (1,087 stars)
PR merge metrics
 (PR metrics pending)

Description

Description

The project currently has excellent test coverage for data validation (4316 tests) but lacks end-to-end (E2E) testing for critical user flows.

Problem

  • No E2E tests exist for interactive features like quizzes, games, search
  • User journeys are not tested from browser perspective
  • Risk of UI regressions going undetected

Proposed Solution

Add Playwright for E2E testing covering:

  • Quiz taking flow (/quizzes/[slug])
  • Game interactions (multiple game pages)
  • Search functionality
  • Navigation across pages
  • Dark mode toggle
  • Mobile responsive behavior

Acceptance Criteria

  • Install and configure Playwright
  • Add E2E tests for quiz completion flow
  • Add E2E tests for at least 2 games
  • Add E2E tests for search
  • Add E2E tests for navigation
  • Configure GitHub Actions workflow for E2E tests
  • Add test documentation

Files to Modify

  • package.json - Add Playwright dependency
  • playwright.config.ts - Create configuration
  • e2e/ - New directory for E2E tests
  • .github/workflows/e2e.yml - New CI workflow

Contributor guide

Research direction
Set up Playwright by following the official guide, create configuration file, and write E2E tests for quiz flow, games, search, navigation, dark mode, and mobile responsiveness. Also configure GitHub Actions workflow.
Tech stack
typescriptnodejsplaywright
Domain
testingci cd
Issue type
Test
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75