Skip to content

ci(frontend): add Playwright HTML test reporting - #2343

Open
anshul23102 wants to merge 1 commit into
utksh1:mainfrom
anshul23102:pr-1701-clean
Open

ci(frontend): add Playwright HTML test reporting#2343
anshul23102 wants to merge 1 commit into
utksh1:mainfrom
anshul23102:pr-1701-clean

Conversation

@anshul23102

Copy link
Copy Markdown
Contributor

Adds HTML reporter configuration to Playwright test suite and enables end-to-end test execution in CI workflow with artifact upload.

Changes:

  • Configure Playwright to generate HTML reports in playwright-report/
  • Run e2e tests as part of frontend-run-checks job
  • Upload Playwright HTML reports as CI artifacts (30-day retention)
  • Include list reporter for console output

This provides visual test failure reports and test execution details for debugging failed e2e tests in CI, improving the developer experience when tests fail in the pipeline.

GSSoC 2026

Adds HTML reporter configuration to Playwright test suite and enables
end-to-end test execution in CI workflow with artifact upload.

Changes:
- Configure Playwright to generate HTML reports in playwright-report/
- Run e2e tests as part of frontend-run-checks job
- Upload Playwright HTML reports as CI artifacts (30-day retention)
- Include list reporter for console output

This provides visual test failure reports and test execution details
for debugging failed e2e tests in CI.
@anshul23102

Copy link
Copy Markdown
Contributor Author

This is a clean, focused version addressing the Playwright HTML test reporting feedback. The previous PR #1701 had unrelated backend/docker changes and failing tests; this version contains only:

  • Playwright HTML reporter configuration (outputs to playwright-report/)
  • E2E test execution in CI workflow (frontend-run-checks)
  • Artifact upload with 30-day retention for failed test debugging
  • List reporter for console output

All CI checks passing. Ready for review.

@utksh1 utksh1 left a comment

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The new E2E step uses continue-on-error: true, so a failing Playwright suite still leaves the required frontend job successful and cannot protect the branch. Please either make E2E failures fail the required job, or move this to an explicitly non-blocking reporting job and document that behavior. Also verify the report upload path when the suite fails.

@utksh1 utksh1 added level:beginner 20 pts difficulty label for small beginner-friendly PRs type:devops DevOps or infrastructure work category bonus label area:ci CI, tooling, or automation work labels Aug 4, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area:ci CI, tooling, or automation work level:beginner 20 pts difficulty label for small beginner-friendly PRs type:devops DevOps or infrastructure work category bonus label

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants