Introduction
One of the most common issues beginners face after running Playwright tests is discovering that no test report is generated. You may notice that the playwright-report folder is missing, the HTML report does not open, JUnit XML files are not created, or reports are missing in GitHub Actions, Jenkins, or Azure DevOps.
If you are facing the Playwright Test Report Not Generating problem, don’t worry—most reporting issues are caused by configuration mistakes, incorrect commands, missing dependencies, or CI/CD artifact settings.
This troubleshooting guide explains how Playwright reporting works, the most common causes of missing reports, and step-by-step solutions with TypeScript examples. You’ll also learn enterprise best practices for generating reliable reports in both local and CI/CD environments.
Why Playwright Reports Are Important
Test reports provide valuable information after execution.
A good report helps you:
- View passed and failed tests
- Identify failed assertions
- Review execution duration
- Open screenshots
- Watch failure videos
- Analyze trace files
- Share results with your team
- Troubleshoot CI/CD failures
Without reports, debugging failed automation becomes much more difficult.
How Playwright Generates Test Reports
When Playwright finishes executing tests, the configured reporter creates output files or directories.
Typical workflow:
Playwright Tests
│
▼
Reporter
│
┌──────┼──────────────┐
▼ ▼ ▼
HTML JUnit JSON
│
▼
Reports Folder
│
▼
Developer / CI Pipeline
The reporter configuration is defined in playwright.config.ts.
Common Reasons Why Playwright Test Reports Are Not Generating
The most common causes include:
- Reporter not configured
- Wrong command used
- Tests never executed
- Browser installation failed
- HTML report folder deleted
- File permission issues
- CI pipeline not publishing artifacts
- Incorrect output paths
- Playwright installation problems
- Reporter package missing (for Allure)
Checking playwright.config.ts Reporter Configuration
The first thing to verify is your reporter configuration.
import { defineConfig } from ‘@playwright/test’;
export default defineConfig({
reporter: [
[‘html’],
[‘list’]
]
});
Step-by-Step Explanation
- html generates the Playwright HTML report.
- list displays execution progress in the terminal.
- Multiple reporters can run simultaneously.
If the HTML reporter is missing from the configuration, no HTML report will be generated.
Running Tests Correctly to Generate Reports
Always execute tests using the Playwright Test Runner.
npx playwright test
After execution:
npx playwright show-report
Explanation
- First command runs all tests.
- Second command opens the generated HTML report.
If you skip test execution, there will be no report to display.
Fixing HTML Report Issues
Problem 1: playwright-report Folder Not Created
Possible Causes
- Tests did not execute.
- Reporter not configured.
- Execution failed before tests started.
Verify:
reporter: [[‘html’]]
Run:
npx playwright test
Check the project directory.
Expected structure:
project
│
├── playwright-report
├── test-results
├── tests
└── playwright.config.ts
Problem 2: HTML Report Not Opening
Run:
npx playwright show-report
If the folder exists but does not open:
- Verify browser permissions.
- Ensure the folder contains index.html.
- Check whether the report path has been customized.
Example:
reporter: [
[‘html’,
{
outputFolder:’reports’
}]
]
Open:
npx playwright show-report reports
Fixing JUnit, JSON, and Allure Report Problems
JUnit Reporter
reporter:[
[‘junit’,
{
outputFile:’results.xml’
}]
]
Verify
- results.xml exists.
- The pipeline publishes the XML file.
JSON Reporter
reporter:[
[‘json’,
{
outputFile:’results.json’
}]
]
Useful for dashboards and custom reporting.
Allure Reporter
Install:
npm install -D allure-playwright
Configure:
reporter:[
[‘line’],
[‘allure-playwright’]
]
Generate the report:
allure generate
Open:
allure open
If Allure reports are not created, verify that the reporter package is installed and that the required CLI tools are available.
Report Generation in GitHub Actions, Jenkins, and Azure DevOps
GitHub Actions
Upload reports as artifacts.
– uses: actions/upload-artifact@v4
with:
name: playwright-report
path: playwright-report
Without artifact upload, reports are usually unavailable after the workflow finishes.
Jenkins
Archive reports.
Example:
archiveArtifacts ‘playwright-report/**’
This preserves reports for later review.
Azure DevOps
Publish build artifacts.
– task: PublishBuildArtifacts@1
inputs:
PathtoPublish: playwright-report
ArtifactName: PlaywrightReport
The reports become downloadable from the completed pipeline.
Debugging Missing Reports, Screenshots, Videos, and Trace Files
Configure Playwright properly.
use:{
screenshot:’only-on-failure’,
video:’retain-on-failure’,
trace:’on-first-retry’
}
Explanation
Screenshot
Captures images only when tests fail.
Video
Stores videos for failed tests.
Trace
Collects browser actions for debugging retry attempts.
If these settings are disabled, related artifacts will not be generated.
Best Practices for Report Configuration
Recommended configuration:
import { defineConfig } from ‘@playwright/test’;
export default defineConfig({
reporter:[
[‘html’],
[‘junit’],
[‘list’]
],
use:{
trace:’on-first-retry’,
video:’retain-on-failure’,
screenshot:’only-on-failure’
}
});
Benefits:
- Rich HTML reports
- CI-compatible JUnit XML
- Console output
- Failure screenshots
- Videos
- Trace Viewer support
Common Mistakes and Troubleshooting Checklist
| Problem | Solution |
| No report generated | Configure the HTML reporter and run tests |
| Report folder missing | Verify test execution completed |
| HTML report won’t open | Use npx playwright show-report and check the output path |
| Empty report | Confirm that tests were discovered and executed |
| Missing screenshots | Enable screenshot capture in use settings |
| Missing videos | Set video: ‘retain-on-failure’ |
| Missing traces | Configure trace appropriately |
| Missing JUnit XML | Check outputFile and artifact publishing |
| Allure report missing | Install and configure allure-playwright |
Real-Time Enterprise Troubleshooting Scenarios
Scenario 1: GitHub Actions Report Missing
Cause
The workflow executed successfully, but the HTML report was never uploaded.
Solution
Add an artifact upload step to the workflow.
Scenario 2: Jenkins Shows Passed Build but No Report
Cause
Artifacts were not archived.
Solution
Archive the report directory after test execution.
Scenario 3: Azure DevOps Does Not Display Reports
Cause
Build artifacts were not published.
Solution
Add a PublishBuildArtifacts task.
Scenario 4: Report Folder Is Empty
Cause
No tests were discovered or all tests were filtered out.
Solution
Verify your test file naming, test command, and filters.
Scenario 5: Reports Work Locally but Not in CI
Cause
Differences in environment variables, permissions, or browser installation.
Solution
Check CI logs, ensure browsers are installed, verify output paths, and confirm artifact publishing.
Playwright Reporting Interview Questions
- What is the HTML reporter?
- How do you enable Playwright reports?
- What is playwright.config.ts?
- How do you open an HTML report?
- Why is the playwright-report folder missing?
- What is the JUnit reporter used for?
- What is the JSON reporter used for?
- What is the Line reporter?
- What is the Dot reporter?
- What is the Blob reporter?
- What is the List reporter?
- What is the Allure reporter?
- How do you publish reports in GitHub Actions?
- How do you archive reports in Jenkins?
- How do you publish reports in Azure DevOps?
- Why are screenshots missing?
- Why are trace files missing?
- What causes empty reports?
- How do you debug report generation failures?
- How do you configure multiple reporters?
- What artifacts should be retained in CI?
- How do you troubleshoot browser installation issues?
- How do environment variables affect report generation?
- What is the difference between HTML and JUnit reports?
- What reporting strategy would you recommend for enterprise automation?
FAQs
Why is my Playwright Test Report not generating?
Common causes include missing reporter configuration, incorrect test execution commands, failed browser installation, permission issues, or CI pipelines that do not publish report artifacts.
How do I generate an HTML report?
Configure the HTML reporter in playwright.config.ts, run npx playwright test, and open the report using npx playwright show-report.
Why is the playwright-report folder missing?
The folder is usually not created if tests did not run, the HTML reporter is disabled, or execution failed before reporting.
Can I use multiple reporters?
Yes. Playwright supports multiple reporters, such as HTML, List, Line, Dot, JUnit, JSON, Blob, and Allure.
Why are screenshots or videos missing?
Ensure screenshot, video, and trace are configured under the use section in playwright.config.ts.
How do I publish reports in CI/CD?
Upload the report directory as a build artifact in GitHub Actions, Jenkins, or Azure DevOps so it can be viewed after pipeline execution.
Is Allure included with Playwright?
No. Allure requires the allure-playwright package and additional report generation steps.
What reporter should I use in enterprise projects?
A common combination is HTML for local debugging, JUnit for CI integration, and List or Line reporters for console output.