WorksheetsBug Reporting Quiz
Total questions: 14
Worksheet time: 7mins
What is the main task of a tester?
To manage the project
To market the product
To check if the product works as intended
To develop software
Which of the following is NOT a basic element of a bug report?
Title
Environment
User feedback
Reproduction steps
What should the title of a bug report include?
The name of the developer
A short, informative description
A detailed description of the bug
The date of the report
What is meant by 'environment' in a bug report?
The version of the product
The team working on the project
The physical location of the tester
The software and hardware setup where the bug was found
How should reproduction steps be written?
In paragraphs
Using bullet points
In numbered format with imperative verbs
As a narrative
What should be included in the 'expected behavior' section?
How the system should behave
The history of the software
What actually happened
The developer's opinion
What is the purpose of including attachments in a bug report?
To showcase the tester's skills
To make the report longer
To confuse the reader
To provide additional context
What is a good practice when writing a bug report?
Using passive voice
Writing in first person
Being objective
Being emotional
What should you do if you find a bug in a specific browser?
Ignore it
Report it without details
Only report it if it happens in all browsers
Include the browser name and version in the report
What is the recommended format for saving evidence of a computer bug?
.mp4 or .avi
.txt or .csv
.docx or .pdf
.png or .jpg
What should you do after writing the reproduction steps?
Recheck the steps to ensure accuracy
Add more details about the bug
Submit the report immediately
Change the title
What is the benefit of using tools for recording actions on a computer?
They slow down the process
They can help provide clear evidence of the bug
They are unnecessary
They are only for advanced users
What should you do if your suggestions are not accepted as bugs?
Argue with the developers
Stop testing
Give up reporting
Continue to report deviations from expected behavior
What is a recommended way to organize a list of defects - which suits the best?
In a physical notebook
In an email
In an Excel sheet or online Google sheet
In a Word document
