The visual analysis section under the video and run reports displays the generated visual bug reports.
View the visual bug reports
To see the generated visual report for runs from videos:
- Click the Videos section under the project in the side menu.
- Here you see the overview of Videos.
- The number of visual issues detected is listed under Visual issues.
- Select the video report you want to see reports from.
- Click View report.
- This opens the run report.
- Scroll to the section Visual analysis where the reports are listed.
To see the generated visual report for runs from game builds:
- Click the Runs section under the project in the side menu.
- Here you see the overview of runs.
- The number of visual issues detected is listed under Visual issues.
- Select the run report you want to see reports from.
- Click View report.
- This opens the run report.
- Scroll to the section Visual analysis where the reports are listed.
Each generated report includes a description of the potential issue identified with the following elements:
- Title, summarizing the issue
- Severity, rated with minor, major, critical, or blocker
- Description of the issue
- Observed, a short description of what is observed as an issue in the screenshot.
- Expected behavior, a short description of what the system expects as correct.
- Video timestamp that corresponds to the video length.
- Screenshot, that is the basis of the report. Click the image to enlarge it, if needed.
For each report, you can provide feedback or push the report to Jira. Refer to the section below for further instructions on how to perform these actions.
Feedback on visual bug reports
Provide feedback on visual bug reports to help improve the accuracy of report generation over time.
Assess the relevance and accuracy of each visual bug report by responding to the prompt "Valid bug?" with a thumbs up or down:
- Click 👍 Yes when:
- The visual bug report accurately identifies an issue visible in the screenshot.
- The description clearly and correctly explains the problem.
- Click 👎 No when:
- The report is inaccurate, irrelevant, or describes a non-issue.
- The screenshot does not correspond to the described problem.
The feedback is recorded and the report is saved as an example for future analysis of videos and build runs.
The saved example reports can be reviewed on the Example reports.