I have attached what my pipeline looks like on DevOps and my config file on VSCode.
Thanking all playwrightians in advance. 🙂
This thread is trying to answer question "Why do tests pass locally but fail on the CI pipeline, and how can the trace file generated from the pipeline be opened and attached to the JUnit results?"
Hi, Azure DevOps does not support JUnit attachments. (Not sure if Playwright even puts references to the traces in the JUnit output, but it does not matter.)
You need a separate step for uploading the zip files with the traces somewhere. I suppose the easiest way to get started is to use the publish artifacts task for that.
I believe others are publishing the HTML report + trace files to GitHub Pages. That would be a more convenient way to access them.
We are publishing them to Azure blob storage, but I cannot share the code.
I don't know if Azure DevOps has the equivalent of GitHub Actions Artefacts to generate and give access to thing along a build.
However I can recommend you to use Argos + Playwright (https://argos-ci.com/playwright). It uploads failures screenshots and traces and give you instant access to it when you run test on CI. We made it for this specific use case!
Rayrun is a community for QA engineers. I am constantly looking for new ways to add value to people learning Playwright and other browser automation frameworks. If you have feedback, email email@example.com.