The document provides best practices for creating bug reports, including defining what a bug is, how to classify bugs by severity and priority, and how to structure an effective bug report. It then provides examples of properly structured bug reports with title, steps to reproduce, expected and actual results, assignee and priority. The document demonstrates how to write clear, informative bug reports that will help developers identify and resolve issues.

1. Презентація менторів Masters Academy
Best practices in creating bug reports
Master of Code Ukraine

2. Best practices in creating bug reports

3. Bug definition
A software bug is an error, flaw, failure or fault in a computer program or
system that causes it to produce an incorrect or unexpected result, or to
behave in unintended ways.

4. Bugs classification
● Severity
○ Blocker/Critical
○ Major
○ Normal/Moderate
○ Minor/Low
● Priority
○ Blocker/Critical
○ High
○ Normal/Medium
○ Minor/Low

6. ● Blocker/Immediate
● Critical/Urgent
● Major/High
● Medium/Normal
● Minor/Low
● Trivial/Lowest
Priority + Severity

7. Bug Report structure
Title: Action Z is performed incorrectly (how) in Y block/page
Priority: (priority+severity level)
Assignee: Developer who will fix the bug
Environment: Browser title and version, OS title and version
(Pre-conditions: optional)
Steps to reproduce:
1 As admin navigate to link.com
2 Do action X (screenshot.png -optional)
3 Do action Z
Expected results:
Action Z is done correctly (description)
Actual results:
Action Z is done incorrectly (description) screenshot.png
(Test Data: optional)

8. Bug Report example
Title: All folders are displayed in Embed list
Priority: Major
Assignee: Backend Developer Vasyl Koval
Steps to reproduce:
1 As admin navigate to Create New Embed page stage.com/dashboard/embed-codes/new
2 Select Channel Embed option
3 Open dropdown to select folder
Expected results:
Only correct folders are displayed in the list (not empty and only added to Library if talking about Marketplace
folders)
Actual results:
All Marketplace folders, even not added to Library are displayed in the list screenshot.com

9. Practical
part 1

11. Title: All bids option is displayed twice in status selector
in app on screen where user can select Bid status
Assignee: PM Nikita Mikhalkov
Priority: Major
Steps to reproduce:
1 Open Make a Bid screen in app stage.com/dashboard/embed-codes/new
2 Click on Type menu item
3 Scroll dropdown to see All Bids options
Expected results:
All bids option is displayed correctly
Actual results:
All bids option is displayed twice in status selector in app on screen where user can select Bid
status

13. Title: “Follow Us” buttons are of a different size
Assignee: Backend developer Max Savchenko
Priority: Major
Steps to reproduce:
1 Check Follow us buttons on site
Expected results:
All Follow us buttons have same size
Actual results:
All buttons are different

15. Title: Filters show results wrongly
Assignee: Backend developer Max Savchenko
Priority: Major
Steps to reproduce:
1 Go to City Managment page stage.com/admin/city/edit
2 Add filter “HAS DC” to City List table
Expected results:
Appropriate results are displayed (those that correspond the filter)
Actual results:
Two cities that match the filter are not diaplayed.

17. Title: Note Text field is highlighted with red color when
focus is on other page element
Assignee: Project Manager Oleg Onoprienko
Priority: Major
Steps to reproduce:
1 Click on any page element on the page
Expected results:
Text field is displayed correctly
Actual results:
Note Text field is highlighted with red color when focus is on other page element

19. Title: Admin credentials are prepopulated for any user
who tries to log in into the system admin area
Assignee: Backend developer Dmytro Voytsek
Priority: Major
Preconditions:
Open Incognito Window in browser to make user browser prepopulation doesn’t work
automatically
Steps to reproduce:
1 As non logged-in user navigate to login page stage.com/login
2 Click on any field
Expected results:
Login form fields stay empty. Prepopulation doesn’t work.
Actual results:
Admin credentials are prepopulated for any user who tries to log in into the system admin
area

21. Title: Email text contains fraud warnings
Assignee: Backend developer Max Savchenko
Priority: Major
Steps to reproduce:
1 Send yourself an email
2 Open email
3 Scroll to the very bottom of the email
Expected results:
No fraud warning is displayed in email footer
Actual results:
Fraud warning is displayed in email footer. It shouldn’t be displayed there

22. Practical
part 2

43. Lorem Ipsum Dolor Sit Amet, Consectetur Adipiscing Elit.
Nulla Vel Leo Pellentesque, Euismod Mauris Ut, Posuere Tortor.
Vivamus est ligula, dictum ac eleifend vitae, venenatis eget neque. Pellentesque interdum
urna at mi consequat condimentum. Praesent rutrum lectus metus, nec faucibus turpis
tempus id. Orci varius natoque penatibus et magnis dis parturient montes, nascetur
ridiculus mus. Sed pharetra dui sit amet ullamcorper placerat. Cras et magna blandit mauris
vehicula dictum. Curabitur elementum metus eget diam molestie cursus.
Aenean convallis orci vel orci congue gravida.
In ullamcorper elit sit amet nisl ultrices iaculis. Nam rutrum dictum vehicula. Vestibulum quis
tellus tincidunt, ultricies mi aliquet, dignissim purus. Pellentesque et ante suscipit, feugiat
magna non, elementum dui. Nunc eros ligula, porta nec diam ut, mollis eleifend odio. Nulla
in mauris porttitor, dignissim dolor id, cursus diam. Fusce tempor, nulla nec pharetra luctus,
lectus ipsum vestibulum felis, sit amet interdum ante velit eget tellus.

48. Practical
part 3

50. Advanced task