Scribd
Upload
1K views2 pages

Utest-Bug Report

A bug report contains information to understand, reproduce, and fix a bug. It includes fields like the issue title, type, steps to reproduce, expected and actual results, and attachments. Testers start with a limit of 5 unapproved bugs per cycle but can submit more as bugs are approved. The limit is removed at higher tester ratings.

Uploaded by

Haribabu Palneedi
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
1K views2 pages

Utest-Bug Report

A bug report contains information to understand, reproduce, and fix a bug. It includes fields like the issue title, type, steps to reproduce, expected and actual results, and attachments. Testers start with a limit of 5 unapproved bugs per cycle but can submit more as bugs are approved. The limit is removed at higher tester ratings.

Uploaded by

Haribabu Palneedi
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

1. What is a Bug Report?

A Bug Report is a written summary of a bug. It contains all the required information
to understand, reproduce, and fix the bug.
To begin your bug report, you just need to click on the blue Report Issue button
from the test cycle header. The bug report form will open.

2. Bug report fields


A bug report contains several fields which need to be filled by the tester properly.
These are the common fields for a bug report:

 Issue Title: A clear description of the bug, testers should follow the title format as
specified in the cycle overview
 Issue Type: Select the type of bug you’re reporting, we already discussed types of
bugs in a previous course. 
 Frequency: Specify how many times the bug can be reproduced. Everytime,
sometimes, etc.
 Priority: Select the severity of the bug, we will discuss each option in the Severity vs
Value course. Sometimes the customer will specify what is critical, high, medium, or
low in the overview, so make sure to read the overview carefully
 Environment: Select the environment where the bug is produced, make sure to
select correct device, browser and OS combination
 Actions Performed: Write down all the actions you performed to produce the bug,
make sure to use numbered steps and start from opening the site or app
 Expected Results: Describe exactly what the user would expect to happen when
carrying out the steps in the actions performed
 Actual Results: Describe exactly what does happen when the user carries out the
steps in the actions performed
 Error Messages: Write down the error message you received, if any
 Additional Environment Info: Use this field to provide any additional information,
keep it empty if there is no additional information
 Attachments: Upload all the attachments required, like screenshots, screen
recordings, logs etc

Once all fields are properly filled, review the report once more and click on
the Submit button.
3. Is there a limit to the number of bugs a tester can report?
Unrated and Rated testers will start out with a limit of 5 unapproved bugs per test
cycle. When one of your bugs gets approved, you will be able to submit one more
bug; so on and so forth. This restriction will be lifted once your tester rating is
increased to a higher rating such as Gold, Silver, Bronze, or Proven rated tester.

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy