diff --git a/docs/dashboards-and-widgets/MostFailedTestCasesTableTop20.mdx b/docs/dashboards-and-widgets/MostFailedTestCasesTableTop50.mdx similarity index 75% rename from docs/dashboards-and-widgets/MostFailedTestCasesTableTop20.mdx rename to docs/dashboards-and-widgets/MostFailedTestCasesTableTop50.mdx index fa963186e..25fe45069 100644 --- a/docs/dashboards-and-widgets/MostFailedTestCasesTableTop20.mdx +++ b/docs/dashboards-and-widgets/MostFailedTestCasesTableTop50.mdx @@ -1,11 +1,11 @@ --- sidebar_position: 14 -sidebar_label: Most failed test-cases table (TOP-20) +sidebar_label: Most failed test-cases table (TOP-50) --- -# Most failed test-cases table (TOP-20) +# Most failed test-cases table (TOP-50) -The widget contains a table with statistical information about the TOP-20 most problematic test cases. +The widget contains a table with statistical information about the TOP-50 most problematic test cases. **Widget's parameters:** @@ -26,7 +26,7 @@ The widget has a table view with the following data displayed: - Last failure - date and time of the last run, when the test item was failed, displayed in 'time ago' format (i.e. "10 minutes ago"). On mouse hover, the system will display accurate start times. - + :::note The widget contains statistics of the most problematic test cases in all launches, except "IN PROGRESS" and "INTERRUPTED" launches. 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. diff --git a/docs/dashboards-and-widgets/WidgetCreation.mdx b/docs/dashboards-and-widgets/WidgetCreation.mdx index ee50d4a94..d703ef03f 100644 --- a/docs/dashboards-and-widgets/WidgetCreation.mdx +++ b/docs/dashboards-and-widgets/WidgetCreation.mdx @@ -39,24 +39,24 @@ There are 15 widget templates in ReportPortal for tracking different KPI: | KPI | Widget template | |----------------------------------------------------------------------------------|------------------------------------------------------------------------| -| Track the reasons of failures | [Launch statistics chart](./LaunchStatisticsChart) | -| Passing rate for filter summary, and structure of problems | [Overall statistics](./OverallStatistics) | -| Track the longest launch in the filter | [Launches duration chart](./LaunchesDurationChart) | -| Track the passing rate and structure of problems of the latest run in the system | [Launch execution and issue statistic](./LaunchExecutionAndIssueStatistic) | -| Track the activity of your QA team | [Project activity panel](./ProjectActivityPanel) | -| Track the growth of new test cases in your build | [Test-cases growth trend chart](./TestCasesGrowthTrendChart) | -| Track the speed of test failure analysis | [Investigated percentage of launches](./InvestigatedPercentageOfLaunches) | -| Follow up information about only important launches for your team | [Launches table](./LaunchesTable) | -| Track new BTS issues in your run | [Unique bugs table](./UniqueBugsTable) | -| Track the most unstable test cases in the build | [Most failed test-cases table](./MostFailedTestCasesTableTop20) | -| See the trend of the number of failed test cases from build to build | [Failed cases trend chart](./FailedCasesTrendChart) | -| See the trend of the number of failed and skipped test cases from build to build | [Non-passed test-cases trend chart](./NonPassedTestCasesTrendChart) | -| Compare two launches together | [Different launches comparison chart](./DifferentLaunchesComparisonChart) | -| Track passing rate for one launch | [Passing rate per launch](./PassingRatePerLaunch) | -| Track passing rate for the build | [Passing rate summary](./PassingRateSummary) | -| Find the most flakiest test in the build | [Flaky test cases table (TOP-20)](./FlakyTestCasesTableTop20) | -| Compare statistics for different builds on one graph | [Cumulative trend chart](./CumulativeTrendChart) | -| Track the most popular failure reasons in the build | [Most popular pattern table (TOP-20)](./MostPopularPatternTableTop20) | -| Track the passing rate of different components of your application | [Component health check](./ComponentHealthCheck) | -| Track the statistics of different components of your application | [Component health check (table)](./TableComponentHealthCheck) | -| Track the top-20 tests with longest execution time | [Most time-consuming test cases widget (TOP-20)](./MostTimeConsumingTestCasesWidgetTop20) | +| Track the reasons of failures | [Launch statistics chart](/dashboards-and-widgets/LaunchStatisticsChart) | +| Passing rate for filter summary, and structure of problems | [Overall statistics](/dashboards-and-widgets/OverallStatistics) | +| Track the longest launch in the filter | [Launches duration chart](/dashboards-and-widgets/LaunchesDurationChart) | +| Track the passing rate and structure of problems of the latest run in the system | [Launch execution and issue statistic](/dashboards-and-widgets/LaunchExecutionAndIssueStatistic) | +| Track the activity of your QA team | [Project activity panel](/dashboards-and-widgets/ProjectActivityPanel) | +| Track the growth of new test cases in your build | [Test-cases growth trend chart](/dashboards-and-widgets/TestCasesGrowthTrendChart) | +| Track the speed of test failure analysis | [Investigated percentage of launches](/dashboards-and-widgets/InvestigatedPercentageOfLaunches) | +| Follow up information about only important launches for your team | [Launches table](/dashboards-and-widgets/LaunchesTable) | +| Track new BTS issues in your run | [Unique bugs table](/dashboards-and-widgets/UniqueBugsTable) | +| Track the most unstable test cases in the build | [Most failed test-cases table](/dashboards-and-widgets/MostFailedTestCasesTableTop50) | +| See the trend of the number of failed test cases from build to build | [Failed cases trend chart](/dashboards-and-widgets/FailedCasesTrendChart) | +| See the trend of the number of failed and skipped test cases from build to build | [Non-passed test-cases trend chart](/dashboards-and-widgets/NonPassedTestCasesTrendChart) | +| Compare two launches together | [Different launches comparison chart](/dashboards-and-widgets/DifferentLaunchesComparisonChart) | +| Track passing rate for one launch | [Passing rate per launch](/dashboards-and-widgets/PassingRatePerLaunch) | +| Track passing rate for the build | [Passing rate summary](/dashboards-and-widgets/PassingRateSummary) | +| Find the most flakiest test in the build | [Flaky test cases table (TOP-20)](/dashboards-and-widgets/FlakyTestCasesTableTop20) | +| Compare statistics for different builds on one graph | [Cumulative trend chart](/dashboards-and-widgets/CumulativeTrendChart) | +| Track the most popular failure reasons in the build | [Most popular pattern table (TOP-20)](/dashboards-and-widgets/MostPopularPatternTableTop20) | +| Track the passing rate of different components of your application | [Component health check](/dashboards-and-widgets/ComponentHealthCheck) | +| Track the statistics of different components of your application | [Component health check (table)](/dashboards-and-widgets/TableComponentHealthCheck) | +| Track the top-20 tests with longest execution time | [Most time-consuming test cases widget (TOP-20)](/dashboards-and-widgets/MostTimeConsumingTestCasesWidgetTop20) | diff --git a/docs/dashboards-and-widgets/img/widget-types/MostFailedTestCases.png b/docs/dashboards-and-widgets/img/widget-types/MostFailedTestCases.png new file mode 100644 index 000000000..23834b3a1 Binary files /dev/null and b/docs/dashboards-and-widgets/img/widget-types/MostFailedTestCases.png differ diff --git a/docs/dashboards-and-widgets/img/widget-types/MostFailureTestCasesTable.png b/docs/dashboards-and-widgets/img/widget-types/MostFailureTestCasesTable.png deleted file mode 100644 index b16c333ee..000000000 Binary files a/docs/dashboards-and-widgets/img/widget-types/MostFailureTestCasesTable.png and /dev/null differ