25 Questions
What should you do after submitting a bug report into the client bug database?
Add a new entry in the bug tracker
What should you do if you find a bug during testing that has already been reported?
Ignore it and proceed with testing
What is the purpose of having a senior tester or lead vet a bug report?
To provide feedback and learning opportunities
What should be included in the bug summary following the PAL format?
Problem, Action, Location
What is a key aspect of 'Expected Results' in a bug report?
Politely asking for the issue to be fixed without specifying how
Why should attachments be included in bug reports?
To highlight errors and help viewers see issues directly
What is the purpose of 'Steps to Reproduce' in a bug report?
To list the actions needed to create the bug
What does the 'Reproduction rate' section in a bug report indicate?
The frequency at which the bug occurs when reproduced
What would be a consequence of not adding an entry in the internal bug tracker after reporting a bug?
There will be difficulties tracking reported bugs internally
In bug reporting, it is recommended to have someone else reproduce your bug to ensure it's not due to your settings or device.
True
Bug summaries should aim to provide detailed explanations of the issue without following any specific format.
False
In a bug report, the 'Steps to Reproduce' section typically should not exceed 10 steps.
True
A bug template is usually unique to each project and provides guidance on how to report bugs.
True
Bug reports do not require the inclusion of screenshots or videos as evidence of the reported issue.
False
Testers should always start the 'Steps to Reproduce' section with '1. Launch game/application' as the first step.
True
The 'Expected Results' section of a bug report should always start with the word 'Please ensure' and end with 'as intended'.
True
Adding a red square box around the issue in a screenshot attachment is optional in bug reporting.
False
After writing a bug report, it is not necessary to have it vetted by a senior tester or lead.
False
Bug summaries in bug reports should follow the PAL format.
True
Adding an entry in the internal bug tracker is optional after reporting a bug.
False
Bug reports can be sent directly to the client without any vetting process.
False
Match the bug report section with its purpose:
Steps to Reproduce = Provide a step-by-step walkthrough Observed results = Explain what happens due to the bug Expected results = Include what is expected without the bug Keywords = Help with future research and client understanding
Match the following bug report sections with their corresponding content:
Steps to Reproduce = List of actions needed to reproduce the bug Observed Results = Description of what happens as a result of the bug Expected Results = Explanation of what is expected to happen without the bug Reproduction Rate = Representation of how often the bug occurs when reproduced
Match the bug database terms with their descriptions:
Internal Bug Tracker = Tool used to log and monitor reported bugs internally Bug Database = Centralized system for storing, tracking, and managing bugs
Match the type of project documentation with its purpose:
Bug template = Guide on how to report bugs with specific steps and sections Bug database = Stores reported bugs for search and reference purposes Bug summary = Brief title using the P.A.L format to describe the issue Internal bug tracker = Optional tool for tracking bugs within the project team
Learn how to effectively write bug reports by thinking about the different words and phrases others might use. This quiz will help you practice coming up with keywords for bug reports, which can prevent duplicate efforts and improve communication on projects.
Make Your Own Quizzes and Flashcards
Convert your notes into interactive study material.
Get started for free
