Want to know how good you are at bug reporting ? Take a quick test and find out!!!
Congratulations - you have completed .
You scored %%SCORE%% out of %%TOTAL%%.
Your performance has been rated as %%RATING%%
Your answers are highlighted below.
Question 1 |
Do you report bugs in a bug tracking software or do you track bugs in a spread sheet that is stored on sharepoint or shared drive ?
Spread sheet in Shared Drive or SharePoint | |
Bug tracking tool Hint: Like QC, Clear Quest, Bugzilla etc., |
Question 1 Explanation:
Tracking bugs in a spread sheet will work for very small projects and will be very difficult to track changes. There are many open source and free bug tracking tools that can be used, it's time for you to suggest your project manager to use a bug tracking software.
Question 2 |
Are you allowed to report bugs directly in bug tracking tool, without bug report being reviewed by your peer or Test Lead ?
Submit bug independently | |
Submit bug after review by Peer or test lead |
Question 2 Explanation:
If you are allowed to report bugs directly in bug tracking tool without it being reviewed by your peer or test lead, means your Test lead / Test manager acknowledges you can write good bug reports. If not, then you have to develop skills required for bug reporting.
Question 3 |
Do you understand Bug life cycle followed in your project and all the different states of a bug ? Can you draw flowchart of the bug life cycle right now (without referring to the bug tracking tool or any other documentation ) ?
Yes | |
No |
Question 3 Explanation:
Understanding bug life cycle, defect states is very important and a must for testers and test leads.
Question 4 |
Do you write "Steps"/"Steps to reproduce" in all of your bug reports ? even for minor defects ?
Yes | |
No |
Question 4 Explanation:
Steps / Steps to reproduce is a must for every bug report, we cannot presume that a developer will follow exact steps a tester to find the reported bug. Not including steps to reproduce increases changes or developer rejecting bug as not reproducible or reassign bug to tester to provide more details.
Question 5 |
Do you attach screenshots/snapshots of the screen and highlight/circle the text or error message ?
No, I do not attach screen shots as i provide details in steps | |
Yes, i attach screen shots but do not highlight/circle before attaching to bug report | |
Yes, i highlight/circle text or error before attaching screenshot to bug report |
Question 5 Explanation:
Always attach screenshots, remembers a picture is worth 1000 words, make life easier for developer. Also screenshots serves as a proof.
Question 6 |
Before reporting a bug, do you always check in bug tracking tool if the bug you have to report is already reported by somebody ?
No (i dont think its needed, as developer will reject it if its duplicate) | |
Yes (I always check before reporting a new bug) |
Question 6 Explanation:
Yes, during bug scrub, duplicate bugs will be caught and rejected. As a tester, it’s your responsibility to make conscious effort not to report duplicate bugs.
Question 7 |
Do you monitor for errors in error logs and attach relevant portion of the error log while reporting a bug ?
No (because i dont have access to error logs) | |
No (i dont as developers them selves can look into error logs) | |
Yes (i do monitor and attach error logs) |
Question 7 Explanation:
Monitoring error log and attaching relevant portion of the error log enables the developer to analyze the issues faster.
Question 8 |
Do you maintain traceability matrix between Requirements, Test Cases and bugs, for the bug that you reported ?
No, I don't understand what traceability matrix is | |
No, we don't maintain traceability matrix in our project or company | |
Yes, I ensure traceability is maintained between Requirements, Test Cases and bugs that i report |
Question 8 Explanation:
Traceability matrix is the key for success of a project. By maintaining traceability between Requirements, Test Cases and bugs, we can ensure all the related test cases and requirements are tested once the associated bug(s) are fixed.
Question 9 |
Do you check for Spelling and grammar before submitting your bug report ?
No (there is no provision in the bug tracking tool) | |
No (I don't think this is important) | |
Yes (I do for every bug report that I submit) |
Question 9 Explanation:
Spelling and Grammatical errors should be corrected before submitting bug report. Otherwise you as tester pass on wrong message about you, your testing team to developers or anybody reading the bug report.
Question 10 |
Do you combine more than 1 bug in a single bug report ? e.g. you find cosmetic errors on Login page and Home page of the application, what would you do ?
Report 1 bug (Log 1 bug and mentioning both cosmetic issues in the same report) | |
Report 2 bugs (Log separate bugs for both cosmetics issues) |
Question 10 Explanation:
Always log separate bug reports for bugs found on different functionality or on different pages. As developers responsible to fix issues can be different for each of the bugs reported in a single bug report.
Question 11 |
Do you mention details of the Test Data used for your testing in your bug report ? e.g. Account id, report start and end dates etc., that you used for testing.
Yes | |
No |
Question 11 Explanation:
It is important to provide details of the test data used for testing, like Account number or Start and end dates for generating report etc., This will enable developer to differentiate between issues related to test data and code.
Question 12 |
Before submitting your bug report, do you review it thoroughly ?
Yes (Occasionally, when i am not Busy) | |
Yes (Always) | |
No (As i am busy) |
Question 12 Explanation:
Before submitting bug reports, it is your duty as a tester to review your bug report thoroughly and ensure all the fields are filled correctly. As an example if you select incorrect release# by mistake then the bug may not be noticed by developers or during bug triage meeting.
Question 13 |
Do you make sometime to go through bugs reported by your peers, get to know about existing bugs and to provide feedback for them ?
No (Barely get time to complete my work) | |
Yes (I do go through bug reports reported by others and provide feedback when required) |
Question 13 Explanation:
You get brownies if you are reviewing others defect, you are doing one of the tasks of a test lead!!! If you are a test lead then its your responsibility!!!
Question 14 |
Were there instances where you were asked by your project manager or test lead to correctly assess "Severity" of the bugs you reported ?
Yes (for 1 or more bugs in past 6 months) | |
No (none in past 6 months) |
Question 14 Explanation:
Correct Severity should be assigned while reporting bug. You should always double check with your test lead or test manager on the severity when you are not sure on what severity to be assigned for a defect.
Question 15 |
When you discover a bug, do you repeat the same scenario with different test data or account etc., ?
No (report bug as and when it occurs) | |
Yes (will repeat test with different test data, but will not report bug if application works fine with different test data) | |
Yes (will repeat test with different test data, will log bug even if it works fine with different test data) |
Question 15 Explanation:
It is always good to log defects even if you suspect test data is incorrect, it's developer's job to confirm if its test data issue. However, it is your job to try with different test of test data whenever test case fails and report your observations in the bug report.
Question 16 |
How do you get to know about fixed bugs that you need to retest ? By filtering in bug reporting tool or do you refer to Build notes ?
Bug reporting tool | |
Build notes |
Question 16 Explanation:
Testers should always refer to build notes or email notification from project manager for the details on the bugs fixed in the current build. Defects marked as fixed in bug tracking tool might not have been migrated to Test environment.
Question 17 |
Do you try to minimize size of the attachment before attaching to the bug report ? e.g.: Zipping files reduces size, converting from Bitmap to JPG can reduce file size significantly.
No | |
Yes |
Question 17 Explanation:
As a best practice all attachments should be zipped and attached to bug report. Do not attach screenshot as bitmap instead convert file to JPG and then attach to bug report.
Question 18 |
Do you participate in bug triage meetings ?
No | |
Yes |
Question 18 Explanation:
Do not wait for somebody to invite you to bug triage meetings, ask your manager or test lead to allow you to participate in these meetings. In case they it’s a strict no, then go through the Minutes of meeting of bug triage meeting and discuss with your lead offline.
Question 19 |
In case one of the developers asks for a favour and requests you, not to log a bug that you found, what would you do ?
Will not submit bug in bug tracking tool | |
Will submit bug in bug tracking tool and report incident to project manager and test lead | |
Will convince developer and submit bug in bug tracking tool |
Question 19 Explanation:
Testing team should log all the bugs they find.
Question 20 |
Do you add detailed comments in bug report when you change status of the bug (reopen, or close) ?
No | |
Yes |
Question 20 Explanation:
Comments are very important in bug report. Looking at the comment history any stakeholder should be able to understand what was done with the defect. Comments should have date and name like [2012-05-12, Lakshmi] bug fix verified on build a.b.c and confirmed as fixed. Hence closing the defect....
Once you are finished, click the button below. Any items you have not completed will be marked incorrect.
There are 20 questions to complete.
Readers,
Questions on Bug reporting is provided by Lakshmi (our guest author)
Other Interesting Articles:
4 comments ↓
nice and useful questionaire on bug reporting, thanks
i got 100 out of 100 in this test
thanks for the test, please post more question related to software testing, thanks in advance.
I got 69%, its very very gud experience as tester…I learnt sooo many things from this…Thanks..
Good to know info.. very useful..
Leave a Comment