[DOCS-13939] Update Synthetics Test Details Page screenshots and add AI failure summaries

content/en/getting_started/synthetics/api_test.md

@@ -223,9 +223,9 @@ For more information, see [Using Synthetic Test Monitors][13].
 
 The **API test** and **Multistep API test detail** pages display an overview of the test configuration, the global uptime associated with the tested endpoints by location, graphs about response time and network timings, and a list of test results and events.
 
-To troubleshoot a failed test, scroll down to **Test Results** and click on a failing test result. Review failed assertions and response details such as status code, response time, and associated headers and body to diagnose the issue.
+To troubleshoot a failed test, review the failures on the **Activity** tab or the **Test Runs** tab and click on a failing test result. Review failed assertions and response details such as status code, response time, and associated headers and body to diagnose the issue.
 
-{{< img src="getting_started/synthetics/api-test-failure-5.png" alt="API test failure" style="width:100%;">}}
+{{< img src="synthetics/api_tests/synthetics_api_test_new.png" alt="API test details page showing the Activity tab with global uptime, alert timeline, and a list of recent test runs" style="width:100%;">}}
 
 With Datadog's [APM integration with Synthetic Monitoring][14], access the root cause of a failed test run by looking at the trace generated from the test run in the **Traces** tab.
 

content/en/getting_started/synthetics/browser_test.md

@@ -139,11 +139,9 @@ The example website regularly throws an error causing it to intentionally fail.
 
 The **Browser Test** details page displays an overview of your test configuration, the global and per location uptime, graphs about time-to-interactive and test duration, sample successful and failed test results, and the list of all test results. Depending on the length of your test, you might have to wait for a few minutes to see the first test results come in.
 
-To troubleshoot a [failed test][10], select a failed test result and review the screenshots leading up to the failed step. You can also review potential **[Errors & Warnings][11]**, **[Resources][12]**, and **[Core Web Vitals][13]** to diagnose the issue. 
+To troubleshoot a [failed test][10], review the failures on the **Activity** tab or the **Test Runs** tab. Select an alert from the timeline to see a **What happened?** summary describing the failing step and error message. From the **Next Steps** panel, you can investigate with Bits AI SRE, view the recovery, pause scheduling, or declare an incident. You can also review potential **[Errors & Warnings][11]**, **[Resources][12]**, and **[Core Web Vitals][13]** to diagnose the issue.
 
-In the example below, the test failed as the result of a server timeout.
-
-{{< img src="getting_started/synthetics/browser-test-failure.mp4" alt="Browser test failure" video="true" >}}
+{{< img src="synthetics/browser_tests/synthetics_test_details_sre.png" alt="Browser test details page showing the Activity tab with an alert timeline, failure summary, and Next Steps panel" style="width:100%;">}}
 
 Use Datadog's [APM integration with Synthetic Monitoring][14] to view traces generated from your backend by the test runs from the **Traces** tab.
 
@@ -164,5 +162,5 @@ Use Datadog's [APM integration with Synthetic Monitoring][14] to view traces gen
 [10]: /synthetics/browser_tests/test_results#test-failure
 [11]: /synthetics/browser_tests/test_results#errors
 [12]: /synthetics/browser_tests/test_results#resources
-[13]: /synthetics/browser_tests/test_results#page-performance
+[13]: /synthetics/browser_tests/test_results#test-performance
 [14]: /synthetics/apm/

content/en/synthetics/_index.md

@@ -64,7 +64,7 @@ You can create Synthetic tests in the [Datadog application][1], with the [API][2
 
 API tests allow you to launch [single][4] or [chained][5] requests to perform verifications on your key systems at various network levels: [HTTP test][6], [SSL test][7], [DNS test][8], [WebSocket test][9], [TCP test][10], [UDP test][11], [ICMP test][12], and [gRPC test][13]. 
 
-{{< img src="synthetics/api_test.png" alt="API tests" style="width:100%;">}}
+{{< img src="synthetics/api_tests/synthetics_api_test_new.png" alt="HTTP API test details page showing the Activity tab with global uptime, an alert timeline, and a list of latest test runs" style="width:100%;">}}
 
 ## Record browser tests
 
@@ -99,7 +99,7 @@ Use [Synthetic private locations][15] to monitor internal APIs and websites or c
 
 Use the [integration between Synthetic tests and APM traces][16] to find the root cause of failures across frontend, network, and backend requests.
 
-{{< img src="synthetics/synthetics_traces.mp4" alt="Synthetic Monitoring" video=true style="width:100%;">}}
+{{< img src="synthetics/apm/synthetics_apm_new.mp4" alt="A failed API test with the side panel open on the Trace tab, showing the APM trace generated by the test run with color-coded spans across services" video=true style="width:100%;">}}
 
 ## Access out-of-the-box dashboards
 

content/en/synthetics/api_tests/http_tests.md

@@ -337,6 +337,8 @@ To display your list of variables, type `{{` in your desired field:
 
 A test is considered `FAILED` if it does not satisfy one or more assertions or if the request prematurely failed. In some cases, the test can fail without testing the assertions against the endpoint.
 
+{{< img src="synthetics/api_tests/synthetics_api_test_new.png" alt="HTTP API test details page showing the Activity tab with global uptime, alert timeline, and a list of recent test runs in alert state" style="width:100%;">}}
+
 For a complete list of HTTP and SSL error codes, see [API Testing Errors][12].
 
 ## Permissions