Open Category List

Managing the Results of Test Cycles

3 minutesread

At the completion of a test cycle, your results will be reported in two different areas – within the Issues module in the main Dashboard, and within the Issues tab of the currently selected test cycle.

The first area is available when you first log into the Applause platform, you’ll be taken to your Dashboard, which contains the Issues Module. This is a scroll-able list of all reported issues for your currently selected test cycle, along with the issues status, associated build number, and issue title. The Issues Module can be filtered to display the latest issues reported, issues flagged as Pending, or those flagged as Critical.

ManagingResults1

Clicking on a particular issue will bring you to a https://help.applause.com/working-with-issue-reports/ more detailed bug report, which will allow you to approve, reject, and rate the bug.

The second area, the Issues Page, is accessible by clicking the Issues tab in the navigation bar on the left hand side of the screen.

ManagingResults2

Clicking that tab will bring you to the Issues Page, which grants you a full view of all reported issues, as well as management options.

ManagingResults4

Above the list are different filter options, allowing you to show or hide closed test cases, include resolved issues, or view by assigned products only. You also have the ability to filter by specific builds and specific environments.

Additionally, each issue has a checkbox to the left of it, which allows you the ability to perform batch actions, available under the Actions dropdown menu in the upper left part of the screen. By selecting each issue you wish to modify, you’ll be able to perform the following actions:

  • Export: The Export action allows you to perform a batch export of each issue you’ve selected to either a .csv file, or to your bug tracking system (if configured)
  • Send Issue for Verification: This action gives you the ability to provide the tester with a URL or an updated build which you feel has resolved the reported issue, and requests a fix verification from the reporter of the issue
  • Mark as Resolved: When an issue has been fixed, marking it as resolved will effectively close the issue in the Applause database. Additionally, issues pushed to a Bug Fix Verification will automatically be marked as resolved.

Finally, by clicking on the title of the bug in the list on the Issues Page or within the Issues Module from the Dashboard, you’ll be taken to the actual Bug Report, which contains all pertinent information about the issue. This will allow you to rate the issue, as all new bugs are, by default, unrated and unaccepted. It is also possible, based on your project, that your TTL will have offered a suggestion on what they feel the validity of the issue is – ultimately, the final call is yours.

ManagingResults5

When a new bug is reported, if it looks to be valid after you’ve reviewed it, choose to Approve the issue from the Actions dropdown, and then [ilink url=” https://help.applause.com/bug-ratings-overview/”] rate the issue[/ilink]. It’s important to consider that bug ratings directly affect tester payout and tester ratings. If the bug you’re sent is invalid, out of scope, or the tester didn’t follow instructions, the bug should be Rejected. Additionally, you will be able to Request More Info from the tester who reported the bug, allowing you to ask for specific information from the tester, and giving them the opportunity to supply that information. With that said – if the tester fails to respond in a timely manner, the issue will be Rejected automatically, with the test cycle automatically closes, or is manually closed by your Project Manager or Test Team Lead.

Additionally, the Actions dropdown menu also grants you the ability to edit the bug report, and to request a bug fix verification from the tester, detailed above.

ManagingResults6

0
0
24
3 minutesread

Related Knowledge Base Posts