diff --git a/content/en/synthetics/browser_tests/test_results.md b/content/en/synthetics/browser_tests/test_results.md index 2cf9caf2491..86a8572fbd0 100644 --- a/content/en/synthetics/browser_tests/test_results.md +++ b/content/en/synthetics/browser_tests/test_results.md @@ -40,7 +40,8 @@ In the **History** section, you can see three graphs: - The **Time-to-interactive by location and device** graph displays the amount of time until a page can be interacted with in seconds. For more information about uptime monitoring, see the [Website Uptime Monitoring with SLOs][14] guide. - The **Test duration by location and device** graph displays the amount of time in minutes each location and device takes to complete in a given time interval. -{{< img src="synthetics/browser_tests/history.png" alt="The History and Sample Runs section in the Test Details page" style="width=80%" >}} + +{{< img src="synthetics/browser_tests/history_2.png" alt="The History and Sample Runs section in the Test Details page" style="width=80%" >}} ## Sample results @@ -157,6 +158,23 @@ If your test reaches the maximum execution time, the timeout message indicates t A test result is considered `FAILED` if it does not satisfy its assertions or if a step failed for another reason. You can troubleshoot failed runs by looking at their screenshots, checking for potential [errors](#errors-and-warnings) at the step level, and looking into [resources][17] and [backend traces](#backend-traces) generated by their steps. +### AI failure summaries + + + +When a browser test run fails, Datadog generates an AI failure summary to help you identify the cause and next steps for investigation. Each summary includes: + +- A short explanation of what failed, grounded in run data such as network errors, assertions, and screenshots. +- A classification of the failure as either a **true failure** (a real problem with your application) or a **test misconfiguration** (an issue with the test setup). +- Suggested next steps for troubleshooting. + +AI failure summaries appear on the test run details page for any failing browser test run. Treat them as a starting point for investigation, not as authoritative root cause analysis, because LLM-generated content can contain inaccuracies. + +To share feedback on the accuracy or usefulness of a summary, click the feedback button in the summary panel. + + +{{< img src="synthetics/browser_tests/test_results/ai_failure_summary.png" alt="AI failure summary panel on a failing browser test run" style="width:100%" >}} + ### Compare screenshots To help during the investigation, click **Compare Screenshots** to receive side-by-side screenshots of the failed result and the last successful execution. The comparison helps you to spot any differences that could have caused the test to fail. diff --git a/content/en/synthetics/guide/synthetic-test-retries-monitor-status.md b/content/en/synthetics/guide/synthetic-test-retries-monitor-status.md index cc5d82f5505..43754cb745b 100644 --- a/content/en/synthetics/guide/synthetic-test-retries-monitor-status.md +++ b/content/en/synthetics/guide/synthetic-test-retries-monitor-status.md @@ -17,7 +17,8 @@ To reduce alert fatigue, Synthetic tests can be retried when a test run fails. I With a fast retry, Datadog runs a Synthetic test multiple times before transitioning the test's monitor to alert and sending you a notification. For more information about monitors associated with your Synthetic tests, see [Use Synthetic Test Monitors][3]. -{{< img src="synthetics/guide/synthetics_test_retries/fast_retries.png" alt="Failed test runs with fast retries" style="width:100%;">}} + +{{< img src="synthetics/guide/synthetics_test_retries/fast_retries_2.png" alt="Failed test runs with fast retries" style="width:100%;">}} ## Group evaluations diff --git a/content/en/synthetics/mobile_app_testing/mobile_app_tests/results.md b/content/en/synthetics/mobile_app_testing/mobile_app_tests/results.md index df1751ae708..182e2b67f29 100644 --- a/content/en/synthetics/mobile_app_testing/mobile_app_tests/results.md +++ b/content/en/synthetics/mobile_app_testing/mobile_app_tests/results.md @@ -17,7 +17,8 @@ further_reading: Click on a mobile app test on the [**Synthetic Tests** page][11] to see the Test Details page. The Test Details page contains all the information relating to your test, including test properties, test history, sample runs, and test runs. -{{< img src="mobile_app_testing/test_details_2.png" alt="The Mobile App Test Details page" style="width=80%" >}} + +{{< img src="mobile_app_testing/test_details_3.png" alt="The Mobile App Test Details page" style="width=80%" >}} Test runs appear in a test details page after a Synthetic mobile app test executes. [Sample results](#sample-results) correlate to the latest passed and failed test executions over a time interval and in a specific number of locations and devices. @@ -38,7 +39,8 @@ In the **Properties** section, you can see the test ID, test creation and edit d In the **History** section, you can see the **Global Uptime** graph, which displays the total uptime of all test locations in a given time interval. The global uptime takes into consideration the [alert conditions][4] configured for a test. -{{< img src="mobile_app_testing/history.png" alt="The History graph displays global uptime" style="width=80%" >}} + +{{< img src="mobile_app_testing/history_2.png" alt="The History graph displays global uptime" style="width=80%" >}} ## Sample results @@ -79,7 +81,8 @@ Video replay Every executed test step contains a screenshot of the step action, step action name, step ID, and step duration. -{{< img src="mobile_app_testing/screenshot-and-action.png" alt="Screenshots and actions in the Sample Runs section of the test details" style="width:100%" >}} + +{{< img src="mobile_app_testing/screenshot-and-action_2.png" alt="Screenshots and actions in the Sample Runs section of the test details" style="width:100%" >}} Screenshots can be disabled by checking "Do not capture screenshot for this step" in the **Advanced Options** section. @@ -100,7 +103,8 @@ Click the video icon ▶️ for a failed test run on the [Mobile Application tes Results of steps contain the XML representation of the screen being tested, as well as the ability to hover over the screenshot or the XML to highlight specific elements of the app. Click an element to view additional attributes: -{{< img src="mobile_app_testing/xml_inspector.png" alt="Screenshot of a test result under the Sample Runs section, showing the XML inspector" style="width=80%" >}} + +{{< img src="mobile_app_testing/xml_inspector_2.png" alt="Screenshot of a test result under the Sample Runs section, showing the XML inspector" style="width=80%" >}} ## Crash reports diff --git a/static/images/mobile_app_testing/history_2.png b/static/images/mobile_app_testing/history_2.png new file mode 100644 index 00000000000..24d549421ed Binary files /dev/null and b/static/images/mobile_app_testing/history_2.png differ diff --git a/static/images/mobile_app_testing/screenshot-and-action_2.png b/static/images/mobile_app_testing/screenshot-and-action_2.png new file mode 100644 index 00000000000..24d549421ed Binary files /dev/null and b/static/images/mobile_app_testing/screenshot-and-action_2.png differ diff --git a/static/images/mobile_app_testing/test_details_3.png b/static/images/mobile_app_testing/test_details_3.png new file mode 100644 index 00000000000..24d549421ed Binary files /dev/null and b/static/images/mobile_app_testing/test_details_3.png differ diff --git a/static/images/mobile_app_testing/xml_inspector_2.png b/static/images/mobile_app_testing/xml_inspector_2.png new file mode 100644 index 00000000000..24d549421ed Binary files /dev/null and b/static/images/mobile_app_testing/xml_inspector_2.png differ diff --git a/static/images/synthetics/browser_tests/history_2.png b/static/images/synthetics/browser_tests/history_2.png new file mode 100644 index 00000000000..24d549421ed Binary files /dev/null and b/static/images/synthetics/browser_tests/history_2.png differ diff --git a/static/images/synthetics/browser_tests/test_results/ai_failure_summary.png b/static/images/synthetics/browser_tests/test_results/ai_failure_summary.png new file mode 100644 index 00000000000..24d549421ed Binary files /dev/null and b/static/images/synthetics/browser_tests/test_results/ai_failure_summary.png differ diff --git a/static/images/synthetics/guide/synthetics_test_retries/fast_retries_2.png b/static/images/synthetics/guide/synthetics_test_retries/fast_retries_2.png new file mode 100644 index 00000000000..24d549421ed Binary files /dev/null and b/static/images/synthetics/guide/synthetics_test_retries/fast_retries_2.png differ