QA Introduction

Lesson 3
Bugs Report
How to report a bug?
There are a few considerations or steps to have in mind when a bug is going to be reported:

 Unique ID.
 Title: this should be representative to identify it quickly but not too extensive.
 Description: a brief comment about the issue.
 Steps to reproduce it: includes step by step all the sequence to reproduce the issue.
 Environment: all the information about the environment where the defect was find
indicating if it is testing or production environment, the operative system, the Pc or
device characteristics, etc.
 App Version: the app version that it is being tested.
 Actual Result: the result that currently is being obtained.
 Expected Result: the real behavior that is expected.
 Additional Information: images, videos or logs that can help developers fixing the
defect.

DEFECT REPORT TEMPLATE

In most companies, a defect reporting tool is used and the elements of a report can vary.
However, in general, a defect report can consist of the following elements.

ID Unique identifier given to the defect. (Usually Automated)

Project Project name.
Product Product name.
Release Version Release version of the product. (e.g. 1.2.3)
Module Specific module of the product where the defect was detected.
Detected Build Build version of the product where the defect was detected (e.g.
Version 1.2.3.5)
Summary Summary of the defect. Keep this clear and concise.
Description Detailed description of the defect. Describe as much as possible
but without repeating anything or using complex words. Keep it
simple but comprehensive.
Steps to Replicate Step by step description of the way to reproduce the defect.
Number the steps.
Actual Result The actual result you received when you followed the steps.
Expected Results The expected results.
Attachments Attach any additional information like screenshots and logs.
www.belatrixsf.com | blog.belatrixsf.com - USA | Argentina | Peru
+1 (617) 608 - 1413 (international line)
Page 1
Remarks Any additional comments on the defect.
Defect Severity Severity of the Defect. (See Defect Severity)
Defect Priority Priority of the Defect. (See Defect Priority)
Reported By The name of the person who reported the defect.
Assigned To The name of the person that is assigned to analyze/fix the defect.
Status The status of the defect. (See Defect Life Cycle)
Fixed Build Version Build version of the product where the defect was fixed (e.g.
1.2.3.9)

Real Example over TeamCity Tool

Web Site Bugs Examples

1. Html: for example HTML5 crossbrowsing compatibility
2. Javascript: undefined variables, syntax problems, slow sites, disable sites
3. Security: for example XSS
4. Flash: issues when is disable
5. HTTP Errors: 404 for broken links, 500 for down servers, etc

www.belatrixsf.com | blog.belatrixsf.com - USA | Argentina | Peru

+1 (617) 608 - 1413 (international line)
Page 2
 6. Cookies: cookies without end date or without encryption
7. Site Performance: files to gig, too many js and css, too many request to the server
8. Styles: colours, fonts, layout design, object sizes

Defect Statuses

www.belatrixsf.com | blog.belatrixsf.com - USA | Argentina | Peru

+1 (617) 608 - 1413 (international line)
Page 3