microsoft / microsoft/playwright
[Feature] A proper way to display playwright-html-reports after running a playwright test in Azure DevOps
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 96.3k
- Forks
- 6.5k
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 180
Description
Playwright offers some fantastic features for debugging (html testresults, trace.zip), but we are having a hard time displaying these results inside Azure Devops. Currently, our workflow is: navigating to failed build, downloading artifacts (video, screenshots, trace.zip), opening screenshots and video 1 by 1 and then navigating to trace.playwright.dev, uploading the trace.zip and then start debugging. We would like to be able to navigate to the html-testresults and/or playwright trace viewer with a single click from the build summary. This makes it much easier for all of our team members and organization and keeps our workflow clean and neat, reducing unnecessary steps.
Thanks so much for all the great work!
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing Playwright's HTML report and trace viewer outputs, then examine how Azure DevOps presents artifacts and build summaries. Define whether the integration should provide a single-click link to the HTML report, the trace viewer, or both. Done means the failed-build summary exposes the agreed report views without manual artifact downloading or trace uploads.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, playwright
- Domain
- ci-cd, testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100