This feature is available only to customers who have provided consent to the usage of SnowFlake database. To learn more please contact Customer Success. |
|---|
| Table of Contents |
|---|
...
The Group Coverage Trend Report is the second report type available under Quality Analytics. It displays multiple apps code coverage over time.
...
If none of the above is what you need, you can always select a custom date range. We recommend a minimum of 4 weeks.
Please note that the start date for the data shown in the charts depends on the selected interval (see section below) and is currently limited to the following Monday or the 1st of the month.
Interval
You can select in which intervals you would like to aggregate the data. Options are: 1 week, 2 weeks, 3 weeks, 4 weeks, 1 month. When selecting 1 month, the data shown in the chart will start at the 1st of the relevant month. For the rest of the interval options, the data shown in the chart will start at the following Monday.
Understanding The Data
The report includes two charts: Modified Coverage and Overall Coverage.
...
When examining your group coverage trend, seeing the data in the right context is important. To that end we have added an option to visualize the scope of the change in the modified chart and the scope of the apps that are examined in the overall chart. To add the methods bar to your charts, click on the “Chart elements” and toggle on the “Number of methods” option.
...
Number Of Production Defects
One of the most common KPIs around quality is the number of production defects that were opened against a build or a version. SeaLights now allows you to visualize the number of production defects and compare it to the coverage trend. To add the number of production defects as added bars in your charts, click on the “Chart elements” and toggle on the “Number of production defects” option. You will be required to upload a .CSV file containing the data of the relevant production defects:
The file should contain relevant production defects to the apps and the date range of the report.
Every line in the file should represent a production defect.
There should be a column in a UTC format that includes the date of the defect and is named “Date”.
Once the file is uploaded successfully, the data will appear on the charts. Please note:
The data will be added to both modified and overall coverage charts, as an aggregated bar (no breakdown according to the apps included in the report).
The data is correlated to the coverage using the defect’s date - the production defects bar will be displayed for the date range which is the closest to the defect’s date (the last date range before the defect was created).
...
Automatic Insights
We provide automatic insights in order to help you identify quality risks. Our first insight alerts when large modification took place in a certain app, but was not covered in testing properly. When these incidents are captured, an “INSIGHTS” button will appear near the chart and will include an indication of the number of found insights. When hovering over the chart, a matching indication will be displayed for the relevant interval / build. Clicking on the “INSIGHTS” button, all insights details will appear above the chart, as can be seen in the image below.
...