arrow-left Back to topicQuizReportersCheck yourself1.You're running tests with 4 shards on GitHub Actions. Each shard finishes and you want one combined HTML report. Which reporter setup achieves this?Use reporter: 'html' on all shards and merge the playwright-report folders manuallyUse reporter: 'blob' on CI, upload each shard's blob-report artifact, then run npx playwright merge-reports in a final jobUse reporter: 'json' and write a custom script to combine the JSON filesUse reporter: 'list' — it automatically aggregates shard results to stdout2.In the dot reporter output ··F·±·×, what does ± mean?Test was skipped due to a test.skip() annotationTest is flaky — it failed at least once but passed on a retryTest timed out and was marked as a partial passTest passed with warnings about deprecated API usage3.You configure reporter: [['html', { open: 'on-failure' }]] locally. On CI, the HTML report should generate but never auto-open a browser. What's the standard way to handle this?Use DISPLAY=:0 on CI to suppress browser windowsSet open: process.env.CI ? 'never' : 'on-failure' in the HTML reporter configUse a separate playwright.ci.config.ts file that omits the HTML reporterHTML reporter never opens a browser on CI automatically — no config needed4.How do you configure two reporters to run simultaneously — list output in the terminal AND a JSON file?Set reporter twice: reporter: 'list' and then reporter: 'json' — the second overrides the firstUse an array: reporter: [['list'], ['json', { outputFile: 'results.json' }]]Use reporter: 'list,json' — comma-separated stringReporters can't run simultaneously — pick one per run5.What does the 'github' reporter add on GitHub Actions?Uploads test results to GitHub's testing API for the PR Checks statusAdds inline failure annotations directly to the PR diff — clicking a failure in the Actions summary shows the failing line of codeCreates a GitHub issue for each test failure automaticallyPosts a comment on the PR with the full test results table6.Your CI platform is Azure DevOps and the team wants failures to appear in the Azure Test Plans dashboard. Which reporter produces the right format?html — Azure DevOps can render Playwright HTML reports nativelyjunit — produces XML that Azure DevOps, Jenkins, and similar tools import into their test dashboardsazure — the dedicated Playwright reporter for Azure DevOps integrationjson — Azure DevOps has a built-in JSON test result parser7.You need to post a Slack message with failure details after each test. Which Reporter interface method should you implement?onEnd(result) — called once after the entire run finishesonTestEnd(test, result) — called after every individual test with its resultonStepEnd(test, result, step) — called after each step within a testonError(error) — called when any test throws an error8.You downloaded a playwright-report.zip artifact from a failed CI run. How do you view it?Unzip it and open index.html directly in a browserRun npx playwright show-report playwright-report.zip — it serves the report on a local portUpload it to trace.playwright.dev for remote viewingRun npx playwright extract-report playwright-report.zip first, then use show-reportSubmit answersarrow-left PreviousProjectsWeb serverNext arrow-right