From f9d925ac8ce0f4d279fa5e696dfd3ab35a08f2e8 Mon Sep 17 00:00:00 2001 From: Yuliya_Prihodko Date: Mon, 23 Oct 2023 15:07:50 +0300 Subject: [PATCH] EPMRPP-87233 || Update Most Failed test-cases table widget+fix links --- .../dashboards-and-widgets/PossibleDashboardsInReportPortal.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/dashboards-and-widgets/PossibleDashboardsInReportPortal.mdx b/docs/dashboards-and-widgets/PossibleDashboardsInReportPortal.mdx index 29b921343..6384c110c 100644 --- a/docs/dashboards-and-widgets/PossibleDashboardsInReportPortal.mdx +++ b/docs/dashboards-and-widgets/PossibleDashboardsInReportPortal.mdx @@ -46,7 +46,7 @@ With [**Investigated percentage of launches**](./InvestigatedPercentageOfLaunche [**Test growth trend chart**](./TestCasesGrowthTrendChart) shows you the speed of new test cases creation. -Also, you can create [**"Most flaky test cases"**](./FlakyTestCasesTableTop20) and [**"Most failed test case"**](./MostFailedTestCasesTableTop20) and find the most unstable items which should be taken into account. +Also, you can create [**"Most flaky test cases"**](./FlakyTestCasesTableTop20) and [**"Most failed test case"**](./dashboards-and-widgets/MostFailedTestCasesTableTop50) and find the most unstable items which should be taken into account. Let's assume that you have a lot of test results and a lot of teams.