Course 3: Build Overview

You can view a list of cards containing build details in the “Quality Score by Build” tab. To access more detailed data visualizations about a build, click “Show all details” in the bottom right corner of the relevant card.

Note: The builds are sorted based on their creation date, from the newest to the oldest, allowing you to concentrate on more recent results and trends.

The Issues tab consists of several sections, providing greater insights into the test results for the build.

High level information about the build is displayed to provide context to the results.

• Creation Date

• Date when the last issue was submitted

• Number of test cycles previously activated for the build (this also includes cycles where the build was tested only part of the duration)

• Number of active test cycles currently testing the build

This section provides an overview of the collected issues. The total number of issues is displayed across different phases. You can toggle the results by issue life cycle phases, impacting all other Build Overview sections.

• Submitted - This count includes all collected issues, except those discarded or disputed

• Approved - A member of your Applause management team or a user from your team triages the submitted issues and approves or rejects them. This count includes all approved issues, except those marked as “Won’t Fix

• Exported - Approved issues may be exported to your Bug Tracking System (BTS) either manually or through the integration. This count includes all issues set with a BTS ID, except those marked as “Won’t Fix”

• Not Fixed - Fixing the issue is yet completed or verification for the fix had failed

• Fixed Not Verified - The issue is marked as fixed by the engineering team, however verification for the fix has not yet started/completed

• Fixed and Verified - The issue was provided a fix by the engineering team and the Applause community was able to successfully verify it

By default this is presented for the Approved issue – click the other issue life cycle phases to view the internal Severity/Value distribution for them.

• Severity - Set by the tester when submitting the issue and re-confirmed during triage

• Value - Set by the user approving the issue during triage

Note: Hiding some of these metrics is possible – contact your Applause team if needed.

In case there are some issues still pending triage, this will be indicated. You should complete triage in a timely manner so you can treat the results displayed more reliably (also it increases the Confidence Level for AQS).

The Coverage section enables a deeper dive of the collected results based on technology and location. Examining the results by coverage allows you to better address issues as well as align the testing strategy of future builds.

Offers the distribution of results by the Operating Systems issues reported against. To drill even deeper, hover over the Operating Systems (OS) – mobile OSs will be sliced by device and OS version and desktop OSs will be sliced by web browser and OS version.

Offers a map view highlighting the distribution of results based on the tester country issues were reported from. You may zoom the map in and out and drag it to focus on interest areas.

Issues by Components provides an in-depth view of the results by the components set for the tested product.

Identifying how issues are distributed across components allows you to better address issues as well as align the testing strategy of future builds.

On top of the overall distribution, you may also filter the results by:

• Issue Type (default)

• Severity

• Value

• Priority (where applicable)

The Testing Services section allows you to better understand the testing process. While testing is performed by the Applause Community and driven by your project team, understanding issue accumulations, testing times and triage status keep you informed about the process, allowing you to fine-tune the testing strategy of future builds with your Applause project team.

• Triage, including the overall issue approval rate, distribution of issue approvers between the Applause and your users and an indication of issues still pending triage

• Testing Times, including average cycle duration and time to first and last issues

• Issue Accumulation, offering a timeline of the accumulation of submitted issues at the test cycle level

The Test Cases tab includes detailed information about the test case results for the build.

This section provides an overview of the test case results. You can toggle the results across the stages.

• Published - All published test cases for this build

• Scoped - All the scoped test cases for this build

• Executed Test Cases - The number of all executed test cases

• Executed Test Runs - The number of all test runs executed for this build

This section will allow you to more accurately identify where to focus quality improvement efforts.

This section will show you test case stats by suite.