Create a bug report
Turn a failed run into a filled-in bug report, as a PDF or a spreadsheet.
From a failed run to a bug report
A failed run already holds everything a developer needs: the steps that led there, what was expected, what appeared instead, and how often it failed before.The bug report gathers it into one document, written for a person.
Create one
- 1
Open the run's Confidence Report
Click Bug Report in the banner, or press Ctrl+B.It is the one button for every bug report: the form opens on two destination tiles, Save as a file and Create a Jira issue.This page follows the file; Jira is below.
- 2
Read and adjust the form
Every field is filled in already.Change any of them, add who it is assigned to, and choose PDF or Excel.
- 3
Save
Nothing is written until you click Save.The report goes into the test's results folder by default.
What is filled in for you
| Field | Where it comes from |
|---|---|
| Title | The test and what failed, such as "Visual Assert #3 not found" |
| Description | What failed and why, where in the test, and how much of the test never ran |
| Steps to reproduce | The run's own steps, numbered, up to the failure |
| Status | New, or Known when an earlier run failed the same way |
| Criticality and priority | Higher when an element is missing or an action failed |
| Reproducibility | Always, often, randomly or once, read from the test's history |
| Environment | This computer's Windows, screen and scaling, and the app version |
What you get
A PDF ready to attach to a ticket, or an Excel workbook with the steps and the history in sheets you can filter.Next to it, a zip file holds the evidence: the expected and actual pictures, the difference, and the screen at the moment of the failure.
Send it to Jira
The same report can become a Jira issue instead of a file, without any plugin: GUI Test Runner-Recorder talks to your Jira site directly.Connect Jira to the Confidence Report once, and every failed run's bug report is one click away from your backlog.
- 1
Connect once
In a run's Confidence Report, click Connect Jira beside Bug Report (the bug report form offers it too, under Create a Jira issue).Give the address of any page of your Jira site, your email and an API token (on Jira Data Center, a personal access token).The token is stored encrypted for your Windows account, and nothing goes through our servers.Once connected, the button disappears: Bug Report offers Jira as a destination from then on.
- 2
Choose where it goes
The project, the issue type, the assignee and the priority are read from your Jira site.The report's own priority is matched to your site's.
- 3
Create the issue
Click Create Jira Issue.The issue holds the description, the steps to reproduce, the expected and found pictures with what changed outlined in red, the PDF and the evidence zip.Its key, such as SCRUM-12, then stands in the report's banner where Connect Jira was: click it to open the issue in Jira or to create another, or press Ctrl+J.
When the same defect fails again, its open issue gets a comment instead of a duplicate.In a pipeline, gtr-cli does all of this by itself with --jira on-failure: see Report failures to Jira.
The whole flow with pictures - the connection, an issue made from the app, and TeamCity filing one on every failed build - is the article Connect Jira to the Confidence Report.
Still stuck?Tell us what you were trying to do, and we answer within one working day.Ask our team