The-DevOps-Daily / The-DevOps-Daily/devops-daily

feat: Add E2E tests with Playwright

Open
#527 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement good first issue hacktoberfest
Dominant language
TypeScript
Stars
1.1k
Forks
392
Avg merge
5h 8m
Merged PRs (30d)
121

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

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with package.json and the existing application routes, especially /quizzes/[slug], then review the proposed playwright.config.ts and e2e/ layout. Define coverage for quiz completion, two games, search, navigation, dark mode, and mobile behavior, and use .github/workflows/e2e.yml to verify the suite runs in CI. Done means the listed acceptance criteria and test documentation are complete.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions, playwright, typescript
Domain
ci-cd, testing-qa, web-dev
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.