From b7a49fb3714705c3b487179012c778c5d2922391 Mon Sep 17 00:00:00 2001
From: Jacob Stevenson <jstevenson131@gmail.com>
Date: Tue, 29 Nov 2022 21:02:30 +0000
Subject: [PATCH] docs: Improve usage of PublishTestResults for Azure Pipelines
 (#18241)

---
 docs/src/ci.md | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/docs/src/ci.md b/docs/src/ci.md
index b6287ab7af..df0787f577 100644
--- a/docs/src/ci.md
+++ b/docs/src/ci.md
@@ -319,7 +319,7 @@ jobs:
                   npx playwright test
 ```
 This will make the pipeline run fail if any of the playwright tests fails.
-If you also want to integrate the test results with Azure DevOps, use `failOnStderr:false` and the built-in `PublishTestResults` task like so:
+If you also want to integrate the test results with Azure DevOps, use the task `PublishTestResults` task like so:
 ```yml
 jobs:
     - deployment: Run_E2E_Tests
@@ -337,13 +337,12 @@ jobs:
               inputs:
                 workingDirectory: 'my-e2e-tests'
                 targetType: 'inline'
-                failOnStderr: false
+                failOnStderr: true
                 env:
                   CI: true
                 script: |
                   npm ci
                   npx playwright test
-                  exit 0
             - task: PublishTestResults@2
               displayName: 'Publish test results'
               inputs:
@@ -353,6 +352,8 @@ jobs:
                 mergeTestResults: true
                 failTaskOnFailedTests: true
                 testRunTitle: 'My End-To-End Tests'
+              condition: succeededOrFailed()
+
 ```
 Note: The JUnit reporter needs to be configured accordingly via
 ```ts