Bug Reporting
What is the bug life cycle?
- bug found - bug reported - bug assigned to developer - bug fixed by developer - fix verified by tester - bug closed
How can a tester be sure that bug was fixed?
- execute the steps in the bug report - make sure the fixed bug does not result in new bugs in same area
If you find a bug and the developer says it is as-designed, what can you do?
- find an exact requirement, which defines the way it should be designed - if there is no specific requirement compare to same feature implemented in quality applications (ask your manager which applications to compare to)
Describe the basic elements you put in a defect/bug report?
· Problem Summary / Short Description / Synopsis · Steps to reproduce (Detailed Description) · Severity (Critical, Serious, Minor, Suggestion) · Status (Open, Pending, Fixed, Closed, cannot reproduce, etc.)
How do you write a bug report?
· Rule of WWW - What happened, Where it happened, under Which circumstances · Write one bug report for each fix to be verified · Bug report should be as complete as possible · Bug reports are as concise as possible · Report a bug immediately, do not postpone · Use technical terms, not "people off the street" language
What are the most important parts of a bug report?
· Steps to reproduce · Short Description · Severity · Priority · Status
What should you do if the developer can't reproduce your bug?
-Reproduce it on your computer; -Reproduce on 1-3 other computers; (If you can't reproduce the defect compare the developer's working environment to yours, if they are identical then make sure that steps to reproduce used by both are exactly the same) -Ask developer to debug on QA environment with his/her tools.
Why should tester look for simplest and most general conditions under which bug will be easily reproducible?
-The easier to understand, the better chance it will be fixed -The faster the fix, the better chance it will be done (look for more than just one path to a same problem) -Management pays lots of attention to high visibility routine bugs
Name the 4 levels of Severity
1. Critical/Fatal (crash, data corruption, hang) 2. Serious (workaround) 3. Minor 4. Suggestion/Enhancement
Who can assign/change priority in a bug report?
Development Manager
What needs to be included to make a good bug report?
How to reproduce the bug. Analyze the problem to minimize number of steps to reproduce it. It should be complete, easy to understand, and non-conflicting.
Why do we create bug reports?
In order to get bugs fixed
Name some popular bug tracking tools
Jira, Mantis, Bugzilla, Elementool, Trac, OTRS.
What are the different types of status a bug can have?
Open bug has just been created; Pending bug was assigned, but not ready yet; Fixed/Resolved bug was completed; Closed bug was fixed or closed due to tester's misunderstanding: as designed/duplicate/etc. Can't Reproduce reported, but can't be recreated; Deferred bug confirmed but the effort to correct it may exceed the Return On Investment or a re-design is scheduled for that area of the application
Who can assign/change severity in a bug report?
QA Tester
Why do we need Bug Tracking Database?
Report bugs; To track (retrieve and update) bugs; To make sure bug gets fixed; To run statistical analysis, to monitor & summarize results; To work on quality improvements; As a communication tool; To monitor individual performance.
What does deferred status mean?
The bug is put off until the next build because the feature involved with the bug may be taken out or upgraded.
What is a use case?
Use cases are used by Business Analysts as a format for specifying system requirements. Each use case represents completed business operation performed by user. From the QA prospective we would need to execute End-To-End test to make sure the requirement is implemented.
How do we learn about the expected behavior of the software we are testing?
We learn about expected behavior from requirements and other technical documentation.
What is the Rule of WWW?
What happened, Where it happened, under Which circumstances