Add Playwright E2E smoke tests

[saurabhhhcodes]

Summary

• add a Playwright config for Next.js smoke E2E coverage with CI-friendly env defaults
• cover the landing page GitHub sign-in entrypoint and unauthenticated dashboard redirect
• add authenticated dashboard widget smoke tests with mocked metrics, contribution range interaction, and goal creation request coverage
• add a public profile route smoke test to ensure /u/[username] renders without requiring auth
• add a dedicated GitHub Actions workflow that installs browsers and uploads the Playwright report

Closes #236

Type of Change

• New feature
• Documentation update

Changes Made

• Added playwright.config.mjs
• Added E2E specs under e2e/
• Added .github/workflows/e2e.yml

How to Test

1. node --check playwright.config.mjs e2e/*.js
2. node node_modules/typescript/bin/tsc --noEmit
3. node node_modules/next/dist/bin/next lint
4. In CI, the new E2E / Playwright smoke tests workflow runs npx -y @playwright/test@1.49.1 test

Notes

• I avoided changing package.json/package-lock.json because this workspace does not have npm available locally to safely regenerate the lockfile. The workflow invokes Playwright through npx -y @playwright/test@1.49.1, so existing npm ci remains unchanged.
• Local next build is blocked on this macOS runtime by the existing Next SWC native binary code-signature issue (failed-loading-swc). Type-check and lint complete locally; lint reports only pre-existing warnings in BadgeSection.tsx and CommitTimeChart.tsx.

Checklist

• Linked issue in summary
• npm run lint equivalent passes locally via node node_modules/next/dist/bin/next lint (warnings only, matching current repo behavior)
• No TypeScript errors (node node_modules/typescript/bin/tsc --noEmit)
• Self-reviewed the diff
• Added/updated tests if applicable

[vercel]

@saurabhhhcodes is attempting to deploy a commit to the PRIYANSHU DOSHI's projects Team on Vercel.

A member of the Team first needs to authorize it.

[saurabhhhcodes]

Hi @Priyanshu-byte-coder, this PR is for assigned GSSoC issue #236. Could you please mirror the issue scoring labels when reviewing: gssoc26, level:advanced, and type:testing?

I kept the E2E setup CI-friendly by avoiding lockfile churn and running Playwright through pinned npx @playwright/test; the tests cover the landing auth entrypoint, protected dashboard redirect, mocked authenticated dashboard widgets, contribution range interaction, goal creation, and the public profile route.

[Priyanshu-byte-coder]

@playwright/test is not in package.json — the CI workflow tries to run the config which imports it, causing the ERR_MODULE_NOT_FOUND crash before any tests run.

Fix:

npm install --save-dev @playwright/test

Then commit the updated package.json and lockfile. Also consider adding:

• playwright install --with-deps step in the workflow (or confirm browsers are pre-installed in the CI image)
• A .gitignore entry for playwright-report/ and test-results/

[saurabhhhcodes]

Synced this branch with the latest main so the PR is no longer behind.

Validation after sync:

• node node_modules/eslint/bin/eslint.js . passed with existing warnings only (BadgeSection image optimization warnings and CommitTimeChart hook dependency warning).
• git diff --check passed.

I also tried tsc --noEmit; it currently stops on stale generated .next/types imports for removed/renamed leaderboard routes, which appears unrelated to this E2E-only patch. The E2E files themselves remain isolated under .github/workflows/e2e.yml, playwright.config.mjs, and e2e/*.

[Priyanshu-byte-coder]

Merged! Solid E2E test suite — cookie injection for auth bypass, page.route() for API mocking, proper playwright config, CI workflow with retries.