Quality Analytics - FAQ
- Sarit Ariel
- Nurit Grinstein
This feature is available only to customers who have provided consent to the usage of SnowFlake database. To learn more please contact Customer Success. |
---|
This feature is available only to customers who have provided consent to the usage of SnowFlake database. To learn more please contact Customer Success. |
---|
Below you’ll find answers to the questions we get asked the most about Quality Analytics.
In order to benefit from the Quality Analytics feature, you must first provide consent to the usage of SnowFlake database. Please contact Customer Success in order to get more information and advance the process.
There might be a few reasons for that:
When you are viewing a coverage trend report with 'All Builds' and an interval longer or equal to the date range (e.g 1 month interval on date range of 3 weeks).
When you are viewing a group coverage trend report with an interval longer or equal to the date range (e.g 1 month interval on date range of 3 weeks).
When you are viewing a coverage trend report with 'Reference Builds' and there is only one build selected.
When no builds were found in the selected date range.
Yes, when no builds were found for a specific interval point, these interval points will be presented in the x-axis but will be skipped on the chart line (chart line will become a dotted line).
Same goes when looking at the Modified Coverage chart, in group trend report and in coverage trend report (whether on ‘All Builds' mode or 'Reference Builds’ mode), and there were no code changes on one interval / reference build.
On coverage trend report > ‘All Builds' mode and in group coverage report the calculation is different than in the Dashboard. Interval X takes all code changes from the last build in interval X-1, and takes all coverage from all related test stages (for trend report) or from all selected apps/branches (for group coverage report) that were reported in all builds within interval X. (e.g. Interval of 1 month: coverage in July means all code changes since last build on June and their coverage from all test stages executions reported on builds within July, for trend report, or from all selected apps/branches, for group trend report).
On coverage trend report > 'Reference Builds’ mode the calculation is similar to the Dashboard calculation, when comparing between two builds.
On coverage trend report > 'Reference Builds’ mode the calculation is similar to the Dashboard calculation, when comparing between two builds.
On coverage trend report > ‘All Builds' mode, and on group coverage report, the calculation of each one of the intervals is similar to the TGA calculation. The main difference is that the quality analytics reports include multiple intervals.