remove synthetics test coverage doc page (#30655)

* remove test coverage doc page

* add back page for browser

Author: yirenWang

content/en/synthetics/platform/_index.md

@@ -31,7 +31,7 @@ Explore the [Test Coverage][4] page to gain insights into the overall testing co
 {{< img src="synthetics/test_coverage/browser_actions.png" alt="Test Coverage page with an Overview section, Untested Actions section, and a Tested Actions section" style="width:100%" >}}
 
 ## Connect Synthetic Monitoring testing and APM
-[Connect APM][4] to identify failing synthetic tests directly through to the root causes by digging into related traces.
+[Connect APM][5] to identify failing synthetic tests directly through to the root causes by digging into related traces.
 
 {{< img src="tracing/index/Synthetics.png" alt="Synthetic tests" style="width:100%;">}}
 

content/en/synthetics/platform/test_coverage/_index.md

@@ -1,16 +1,13 @@
 ---
 title: Test Coverage
-description: Evaluate your testing suite's coverage of browser actions and API endpoints.
+description: Evaluate your testing suite's coverage of browser actions.
 aliases:
   - /synthetics/dashboards/testing_coverage
   - /synthetics/test_coverage
 further_reading:
 - link: 'https://www.datadoghq.com/blog/test-coverage-monitoring-datadog/'
   tag: 'Blog'
   text: 'Track your test coverage with Datadog RUM and Synthetic Monitoring'
-- link: 'https://www.datadoghq.com/blog/api-test-coverage-monitoring-datadog-synthetics/'
-  tag: 'Blog'
-  text: 'Improve your API test coverage with Datadog Synthetic Monitoring'
 - link: '/synthetics/browser_tests'
   tag: 'Documentation'
   text: 'Learn about Synthetic browser tests'
@@ -97,61 +94,11 @@ Add the most popular sections of your application to a new or existing browser t
 [8]: https://app.datadoghq.com/rum/explorer/
 [9]: /continuous_testing/
 
-{{% /tab %}}
-{{% tab "API Endpoints" %}}
-
-The [**Test Coverage** page][1] provides actionable insight into the overall testing coverage of your [API endpoints][2]. It uses [data collected from the Software Catalog][2] and [spans from APM][3].
-
-{{< img src="synthetics/test_coverage/api_endpoints.png" alt="Test Coverage page with an Overview section, Untested Actions section, and a Tested Actions section" style="width:100%" >}}
-
-The Test Coverage page presents the following information:
-
-- The overall coverage of your API endpoints
-- The percentage of tested API endpoints
-- The number untested API endpoints with the highest request count, sorted by error rate
-- The percentage of tested API endpoints with API tests that have not been tested in CI
-- The number of untested API endpoints that have [APM monitors][4] 
-
-## Investigate test coverage for API endpoints
-
-Maintain a comprehensive, accurate testing suite by resolving issues that are causing your Synthetic tests to fail and your API endpoints to experience poor performance. 
-
-To identify areas in your testing suite where you should create API tests:
-
-1. Click the **Untested** checkbox in the **API overall coverage** section.
-2. Investigate the endpoint side panel to see all the passing or failing tests that have been created for the endpoint. The **Dependency Map** displays upstream issues that may be contributing to your endpoint's poor performance, and downstream dependencies that are affected.
-3. Identify gaps in your API test coverage by examining the information presented in the following sections: 
-
-   **API Overall Coverage** 
-   : Displays all of the untested endpoints within your tag scope. 
-
-   **Performance**
-   : Displays the most engaged, untested endpoints with significant error rates.
-
-   **Tested in the CI**
-   : Displays the endpoints that are currently being tested in your CI pipelines. 
-
-   **APM Monitors**
-   : Displays the endpoints that are untested but have active monitors on them. 
-
-For more information about the data displayed, see [APM Metrics][5].
-
-## Add tests
-
-To create a test, click **+ New Test** on the top right of the [Test Coverage page][1]. You can run tests [directly in your CI/CD pipelines][6] to ensure no regressions occur before releasing code in production.  
-
-[1]: https://app.datadoghq.com/synthetics/test-coverage/api
-[2]: /api_catalog/monitor_apis/
-[3]: /tracing/
-[4]: /monitors/types/apm
-[5]: /tracing/metrics/
-[6]: /continuous_testing/
-
 {{% /tab %}}
 {{< /tabs >}}
 
 ## Further Reading
 
 {{< partial name="whats-next/whats-next.html" >}}
 
-[1]: https://app.datadoghq.com/synthetics/test-coverage/browser
+[1]: https://app.datadoghq.com/synthetics/test-coverage/browser