Skip to content

[MM-69793] Port blob reporter to v2 branch - #1264

Open
bgardner8008 wants to merge 1 commit into
v2from
MM-69793-e2e-reports
Open

[MM-69793] Port blob reporter to v2 branch#1264
bgardner8008 wants to merge 1 commit into
v2from
MM-69793-e2e-reports

Conversation

@bgardner8008

Copy link
Copy Markdown
Contributor

Summary

  • Switch CI Playwright reporter from html to blob in e2e/playwright.config.ts
  • Copy blob-report (instead of playwright-report) out of the E2E container in e2e/scripts/run.sh

This is the v2 follow-up to PR #1244, which fixed the broken E2E Report Generation workflow on main. The generate-e2e-report.yml workflow always runs from main (GitHub workflow_run semantics) and now expects blob-report artifacts; v2-based feature branches were still producing the old HTML-format artifacts, causing the report generation step to fail with Error: No report files found in .../all-blob-reports.

No changes needed to generate-e2e-report.yml or e2e.yml — the report workflow was already fixed on main, and the artifact upload step picks up results/blob-report-* automatically.

Jira: MM-69793

Switch the CI reporter from html to blob in playwright.config.ts and
copy blob-report out of the container in run.sh, matching the fix
already applied to main in PR #1244.
@codecov-commenter

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
⚠️ Please upload report for BASE (v2@b1159d2). Learn more about missing BASE report.

Additional details and impacted files
@@          Coverage Diff          @@
##             v2    #1264   +/-   ##
=====================================
  Coverage      ?   31.41%           
=====================================
  Files         ?      249           
  Lines         ?    13933           
  Branches      ?     1762           
=====================================
  Hits          ?     4377           
  Misses        ?     9064           
  Partials      ?      492           
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants