How to View Issue Reports


 

During an active test cycle testers will be creating issue reports in the Applause platform. These issue reports will consist of a title, numbered steps to reproduce the issue, expected and actual results, screenshots and/or a video of the issues, as well as any other information requested by you.

You may view issue reports:

How to View Issue Reports Within a Test Cycle
  1. Select a product.
  2. From the left navigation bar navigate to “Test Cycles”.
  3. You may use the search box at the top, show/hide closed cycles and/or re-sort the list by clicking the column headers.
  4. Click on the name of the desired test cycle to view the complete test cycle information.
  5. Open the Issues tab to access the issues.
  6. The issues list will be displayed, containing the issue ID, triage status, severity, value rating and other columns.
    • The columns can be added or hidden using the Configure Columns in the top right corner of the list.
  7. Locate a specific issue and click the issue title to view the complete issue report.

How to View the Global Issues List Across all Test Cycles
  1. Select a product.
  2. From the left-hand navigation bar navigate to “Issues”.
  3. The global Issues list page will be displayed, offering similar functionality to the test cycle view; it also has a column for "Test cycle ID". Clicking on it takes you to the test cycle where this issue was reported.

 

Issue Report Content

The Issue Detail page consists of the following sections:

 

Issue Header and Environments

Let's consider the issue information available in the issue report’s header. Some fields may not be displayed depending on the current state of the issue.

Issue ID

The ID of the issue that is located in the top left corner.

Issue Title

The title of the issue following a specific format required in the cycle overview. It describes the issue briefly.

Resolution

Whether or not the issue has been resolved. It can be changed by clicking on the pencil icon on the right side of the resolution status. The resolution can be: Unresolved, Resolved, Won’t Fix.

Test Cycle

The test cycle page link.

Build

The build of the product the issue was found on.

Testing Type

The testing type of the current test cycle. E.g. Functional, Usability, Localization, etc.

Available Actions

Inside the issue report details page, you can:

Triage

The Triage section shows the final triage status (Approved, Rejected) if the issue has been triaged. Also if a TTL leaves a recommendation on the issue, the recommendation will be shown as well.

If the issue has not been triaged, the appropriate Triage Issue button will be available for you to triage it. And if a TTL leaves a recommendation on the issue, the recommendation will be shown as well.

Status

An indication of the issue’s triage state, like New, Approved, Rejected, Pending, etc.

Approval

The value of the issue assigned by the user who approved the issue during triage.

Severity

An estimate provided by the tester on the impact the issue might have - either Critical, High, Medium or Low.

Frequency

This shows how often the issue occurs.

Issue Type

What kind of issue it is - Functional, Crash, Visual, Content or Performance.

Execution Type

Only the Community type is available as of now. A new type will be added later.

Source

What testing method was used to find the issue, either Exploratory or Test Case.

Tester

The name of the tester that submitted the bug. Clicking on the tester name will bring up the tester profile. Additionally, you can click on the blue badge next to their name to mark them as a Favorite Tester.

Submitted

The time when the issue was submitted.

Component

If the product and test cycle has components enabled, a tester might specify a component here.

Export

In case the issue was sent to your Bug Tracking System (BTS), the issue’s ID in your BTS will be displayed.

Verification

An indication on the fix verification state of the issue; either Requested, Not Requested, Fixed or Not Fixed.

Environments

Where the bug was found - either a mobile device, web browser, etc.

 

Reporting

The Reporting section consists of fields that should contain the main details about the issue report.

Action Performed

This field contains the steps the tester followed to find the issue.

Expected Result

This field describes what the tester expects to happen once the action was taken.

Actual Result

This field describes what actually happened when the action was taken.

Custom Fields

Any number of custom fields can be added, and named as desired. In this case, the Exact URL / App page custom field has been added.

Attachments

This section contains screenshots, videos or log files relevant to the reported issue. Inform your Applause management team if you need specific attachments from testers such as browser/device logs, Charles Proxy logs, videos, screenshots, etc.

Community Reproductions

This is the list of additional reproductions of the issue, often by other testers and environments.

Testers are not obligated to reproduce other testers’ work, however they can document their reproductions should they try to submit a bug and find out it was already submitted.

 

Side Tabs

There are three tabs on the right hand side of the page: Messenger, Notes and Activity.

Messenger

Allows you to communicate with the tester, also the history of the messages from you, the tester and TTL/TE will be displayed here.

Notes

Allows you to communicate with the internal team (Applause team), also the history of the messages from you. Messages sent by using this method will not be shown to community testers.

Activity

The Activity tab provides a track record of any and all changes made on the issue report status and the issue report. All changes, from something as minor as a text field to as major as a change in status, are stored and tracked on this tab except for the attachments.