This thread is trying to answer question "How can one include all files required to create a trace in a GitHub Action?"
https://bmayhew.github.io/playwright-demo/ <- @playwright/test": "^1.38.1", trace files are included
https://github.com/BMayhew/playwright-demo/tree/master repo is here if you want to stare and compare your way to a solution
First, create a GitHub repository and initialize it with
git init. This will let you manage your code.
Next, navigate to the Workflows tab on GitHub to check your test results. Click on the Details link in the PR status check for more information.
To see test logs and error messages, select the workflow run and click on "Run Playwright tests".
To create an HTML report, go to the Artifacts section and download "playwright-report" as a zip file. Extract the zip file into a folder with Playwright installed.
npx playwright show-report <extracted-folder>
This command will serve the report locally for you to view in your browser.
To include all files for creating a trace in a GitHub Action with Playwright CLI or trace.playwright.dev:
npx playwright show-trace trace.zip
npx playwright show-trace https://ray.run/trace.zip
Remember, CORS rules may apply when accessing remote traces.
For more detailed steps, refer to the official Playwright and GitHub Actions documentation.
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.