Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Publish latest changes #630

Merged
merged 3 commits into from
Oct 23, 2023
Merged

Publish latest changes #630

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
63e1e0e
Bump @babel/traverse from 7.21.3 to 7.23.2 (#628)
dependabot[bot] Oct 19, 2023
b64a380
EPMRPP-87233 || Update Most Failed test-cases table widget+fix links …
pressayuliya Oct 23, 2023
66a69cf
Fix links for widgets (#631)
pressayuliya Oct 23, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions ...widgets/MostFailedTestCasesTableTop20.mdx → ...widgets/MostFailedTestCasesTableTop50.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -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:**

Expand All @@ -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.

<media-view src={require('./img/widget-types/MostFailureTestCasesTable.png')} alt="Data visualization in test automation: Most Failed Test Cases Table Widget" />
<media-view src={require('./img/widget-types/MostFailedTestCases.png')} alt="Data visualization in test automation: Most Failed Test Cases Table Widget" />

:::note
The widget contains statistics of the most problematic test cases in all launches, except "IN PROGRESS" and "INTERRUPTED" launches.
Expand Down
24 changes: 12 additions & 12 deletions docs/dashboards-and-widgets/PossibleDashboardsInReportPortal.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -30,27 +30,27 @@ The goal for this test results dashboard to show the status of the latest test r
<media-view src={require('./img/dashboards/LaunchReport.png')} alt="Dashboard to manage test results: Launch Report" />

You can configure:
[**Passing rate widget**](./PassingRateSummary) that shows a passing rate for a latest launch "API suite'
[**Passing rate widget**](/dashboards-and-widgets/PassingRateSummary) that shows a passing rate for a latest launch "API suite'

[**Most popular pattern**](./MostPopularPatternTableTop20) tracks TOP-20 problems in the last and previous runs of this suite.
[**Most popular pattern**](/dashboards-and-widgets/MostPopularPatternTableTop20) tracks TOP-20 problems in the last and previous runs of this suite.

:::note
For Most popular pattern table, you should you create a set of rules and run Pattern Analysis
:::

With [**Investigated percentage of launches**](./InvestigatedPercentageOfLaunches) you can find out the status of failure investigations. You will be able to evaluate team performance and consistency of results.
With [**Investigated percentage of launches**](/dashboards-and-widgets/InvestigatedPercentageOfLaunches) you can find out the status of failure investigations. You will be able to evaluate team performance and consistency of results.

[**Failed cases trend chart**](./FailedCasesTrendChart) shows the history of failures in previous runs.
[**Failed cases trend chart**](/dashboards-and-widgets/FailedCasesTrendChart) shows the history of failures in previous runs.

[**Duration chart**](./LaunchesDurationChart) will be very helpful for those who track duration KPI and want to increase the speed of tests run.
[**Duration chart**](/dashboards-and-widgets/LaunchesDurationChart) will be very helpful for those who track duration KPI and want to increase the speed of tests run.

[**Test growth trend chart**](./TestCasesGrowthTrendChart) shows you the speed of new test cases creation.
[**Test growth trend chart**](/dashboards-and-widgets/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"**](/dashboards-and-widgets/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.

You can create [**Overall statistics**](./OverallStatistics) and [**Launches table**](./LaunchesTable), and now a team who is responsible for API suite has no need to go to the test results. It can use only this dashboard which gives enough information for test failure management.
You can create [**Overall statistics**](/dashboards-and-widgets/OverallStatistics) and [**Launches table**](/dashboards-and-widgets/LaunchesTable), and now a team who is responsible for API suite has no need to go to the test results. It can use only this dashboard which gives enough information for test failure management.

## Build / Release/ Sprint Report (A dashboard for a Team leads, PM, DM)

Expand All @@ -65,20 +65,20 @@ Also, it is very useful to compare the results of the Regression on the current
On this dashboard you can see different metrics:

- A passing rate for the whole Regression
- With [**Cumulative trend chart**](./CumulativeTrendChart) you will be able to compare different versions on one chart, to compare different runs for the current regression
- [**Component Health Check Widget**](./ComponentHealthCheck) would show you product:
- With [**Cumulative trend chart**](/dashboards-and-widgets/CumulativeTrendChart) you will be able to compare different versions on one chart, to compare different runs for the current regression
- [**Component Health Check Widget**](/dashboards-and-widgets/ComponentHealthCheck) would show you product:

* on different env
* on a different dimension
* by business metrics / by features/ by user roles / by etc

Also with a help of [**Component Health Check Widget**](./ComponentHealthCheck) you can create a Test Pyramid.
Also with a help of [**Component Health Check Widget**](/dashboards-and-widgets/ComponentHealthCheck) you can create a Test Pyramid.

:::note
You need to report test executions with attributes which specified needed metrics or envs
:::

- [**Unique bugs table**](./UniqueBugsTable) helps you collect and analyze new bugs in the system
- [**Unique bugs table**](/dashboards-and-widgets/UniqueBugsTable) helps you collect and analyze new bugs in the system

:::note
Component Health Check Widget and Cumulative trend chart are very configurable and you can create your own widget based on project needs.
Expand Down
42 changes: 21 additions & 21 deletions docs/dashboards-and-widgets/WidgetCreation.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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) |
Binary file added docs/dashboards-and-widgets/img/widget-types/MostFailedTestCases.png
View file
Open in desktop
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file removed docs/dashboards-and-widgets/img/widget-types/MostFailureTestCasesTable.png
View file
Open in desktop
Binary file not shown.
Loading