Course 1: How to View Issue Reports
Learn all the details of an issue report and how to view them in the Applause platform.
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 additional info requested by you.
You may view issue reports:
- Within a test cycle
- From the global list containing issue reports across all of your cycles
From the left-hand navigation bar navigate to “Test Cycles”.
Search for your test cycle on the list. You may use the search box at the top, show/hide closed cycles and/or re-sort the list by clicking the column headers.
Select the “Test Cycle name” to view the complete test cycle information.
Click the “Issues tab” to access the issues.
The issues list will be displayed, containing the issue ID, status, severity, value rating, BTS identifier (if exported), BFV status (if verified), build, source, app component, +1s and messages.
Locate a specific issue and click the issue title to view the complete issue report.
From the left-hand navigation bar, navigate to “Issues”.
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.
The Issue Detail page allows you to review the tester’s findings in the following sections:
- Issue Header
Let's consider the issue information available in the header of the issue report. Some fields may not be displayed depending on the current state of the issue.
The ID of the issue that’s located in the top left corner.
The time when the issue was reported.
The ID of the test cycle.
The title of the issue following a specific format required in the cycle overview. It describes the issue briefly.
The name of the tester that submitted the bug. Clicking on the tester's name will bring up the tester profile. Additionally, you can click the blue badge next to their name to mark them as a Favorite Tester.
Where the bug was found - either a mobile device, web browser, etc.
The build of the product the issue was found on.
The name of the product being tested.
What kind of issue it is - either Functional, Crash, Visual, Content or Performance.
What testing method was used to find the issue, either Exploratory or Test Case.
An estimate provided by the tester on the impact the issue might have - either Critical, High, Medium or Low.
Whether or not the issue has been resolved.
In case the issue was sent to your Bug Tracking System (BTS), the issue’s ID in your BTS will be displayed.
An indication of the triage state of the issue, either New, Approved, Rejected, Pending, etc.
The value of the issue, assigned by the user who approved the issue during triage.
An indication on the fix verification state of the issue, either Requested, Not Requested, Fixed or Not Fixed.
The content provided by the tester consists of the comprehensive details of the issue report and includes the following information.
This is a list of outcomes for initial triage by your Applause management team, ensuring the issue was in scope, it is reproducible, not a duplicate and the suggested value for the issue.
This shows how often the issue occurs.
This field contains the steps the tester followed to find the issue.
This field describes what the tester expects to happen once the action was taken.
This field describes what actually happened when the action was taken.
This field is for error messages displayed to the user, if any.
This can be used to detail any other information the tester feels is necessary to pass along. Additionally, inform your Applause management team if you need specific information from testers.
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 logs, Charles Proxy logs, videos, screenshots, etc.
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 will gladly document their reproductions.
The History tab provides a track record of any and all changes made on the issue. All changes, from something as minor as a text field to as major as a change in status, are stored and tracked on this page except for the attachments.