# Publishing Playwright report as an artifact in Azure DevOps

1. [Creating a multi-stage YAML pipeline in Azure DevOps for .NET projects](https://bogdanbujdea.dev/creating-a-multi-stage-yaml-pipeline-in-azure-devops-for-net-projects?source=more_series_bottom_blogs)
    
2. [Running tests with code coverage in Azure DevOps YAML pipelines](https://bogdanbujdea.dev/running-tests-with-code-coverage-in-azure-devops-yaml-pipelines?source=more_series_bottom_blogs)
    
3. [Static code analysis with NDepend in Azure Pipelines](https://bogdanbujdea.dev/static-code-analysis-with-ndepend-in-azure-pipelines?source=more_series_bottom_blogs)
    
4. [Running e2e tests with Playwright in Azure YAML Pipelines](https://bogdanbujdea.dev/running-e2e-tests-with-playwright-in-azure-yaml-pipelines?source=more_series_bottom_blogs)
    
5. [Publishing Playwright report as an artifact in Azure DevOps](https://bogdanbujdea.dev/publishing-playwright-report-as-an-artifact-in-azure-devops?source=more_series_bottom_blogs)
    
6. [Bicep Infrastructure Deployment from Azure DevOps YAML Pipelines](https://bogdanbujdea.dev/bicep-infrastructure-deployment-from-azure-devops-yaml-pipelines?source=more_series_bottom_blogs)
    
7. [Blue-green Deployments in Azure DevOps YAML Pipelines](https://bogdanbujdea.dev/blue-green-deployments-in-azure-devops-yaml-pipelines?source=more_series_bottom_blogs)
    
8. [Pre-Deployment Health Checks in Azure DevOps YAML Pipelines](https://bogdanbujdea.dev/pre-deployment-health-checks-in-azure-devops-yaml-pipelines?source=more_series_bottom_blogs)
    
9. [Azure DevOps Best Practices: Breaking Down the Monolithic YAML](https://bogdanbujdea.dev/azure-devops-best-practices-breaking-down-the-monolithic-yaml?source=more_series_bottom_blogs)
    

---

To store the Playwright report as an artifact we just need to publish the folder where the results of the tests are stored:

```yaml
- publish: $(System.DefaultWorkingDirectory)/<path-to-e2e-report-folder>
  artifact: playwright-report
```

Once the pipeline is finished you can see the report published in the artifacts section:

![](https://cdn.hashnode.com/res/hashnode/image/upload/v1677245199772/8847f58e-a80c-44bb-8603-69328c92d8e7.png align="center")

The folder contains an index.html file with the results which you can simply open in the browser of your choice.