Skip to content

Commit 15a0f9a

Browse files
Merge pull request #307271 from ninallam/patch-8
Include AI-based error insights in load test documentation
2 parents 696bb11 + 94bdaf3 commit 15a0f9a

1 file changed

Lines changed: 5 additions & 0 deletions

File tree

articles/app-testing/load-testing/how-to-diagnose-failing-load-test.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -100,6 +100,11 @@ Use the following steps to help diagnose a test not finishing:
100100
1. [Download and analyze the test logs](#download-apache-jmeter-or-locust-worker-logs-for-your-load-test) to identify issues in the JMeter test script.
101101
1. [Download the test results](./how-to-export-test-results.md) to identify issues with individual requests.
102102

103+
You can also view AI-based error insights for your test run after a test run completes. The insights generated contain the cause of error and more actionable recommendations. Refer to [Microsoft Privacy Statement](https://go.microsoft.com/fwlink/?LinkId=521839)
104+
105+
> [!NOTE]
106+
> By agreeing to use AI-based error insights, you agree that the log files for your test run will be used by AI to generate recommendations.
107+
103108
### Load test completed
104109

105110
A load test might run the test script until the end (test status equals *Done*), but might not pass all the [test fail criteria](./how-to-define-test-criteria.md). If at least one of the test criteria didn't pass, the *test result* of the test run is set to *Failed*.

0 commit comments

Comments
 (0)