Published on February 17, 2014
Finding bugs, categorizing bugs and writing good bug reports http://qtp.blogspot.com
How to find critical bugs? How to categorize bugs? http://qtp.blogspot.com How to write a good bug report?
How to find critical bugs? http://qtp.blogspot.com
understand the functionality in-depth so that you know all the ins & outs of the AUT http://qtp.blogspot.com
domain knowledge is a serious advantage http://qtp.blogspot.com
attack the application with incorrect data, for example: use numeric data where only words can be entered, use v e r y l o n g data in character fields, try entering gibberish data or special characters, empty spaces etc. http://qtp.blogspot.com
load /stress test the AUT to see where the performance actually breaks or degrades. And was this expected? http://qtp.blogspot.com
run tests http://qtp.blogspot.com
use different browsers & environments http://qtp.blogspot.com
How to categorize bugs? http://qtp.blogspot.com
Priority how bad a bug is? both are independent of each other Severity importance of fixing a bug http://qtp.blogspot.com bug should be categorized properly as per both priority & severity
Lets have a look at Severity http://qtp.blogspot.com
Showstopper issue for which no workaround is available issue that blocks some important functionality of any application or major module (Severity 1) issue that affects all users for example not able to login, not able to deploy a build http://qtp.blogspot.com
issue that affects major functionality in an application issue for which there might be a workaround it also typically affects all users and prevents testing of a main use case for example there's an exception on clicking a button on a page, an important service is not available frequently http://qtp.blogspot.com
issue for which there is a workaround issue which does not affect the main functionality Medium (Severity 3) all features can be used with little added effort for example if any action in an application generates history and that generation of history is somehow not working in the application http://qtp.blogspot.com
Low (Severity 4) issue that may or may not be fixed depending on time, risk, resources etc issue which does not have a noteworthy effect on the functionality of the product for example any cosmetic issue or some thing not at all severe like spelling mistake or color inconsistency for couple of fields etc http://qtp.blogspot.com
Lets have a look at Priority http://qtp.blogspot.com
Priority 1 critical loss or corruption of client data etc needs to be fixed by EOB today, cannot wait to fix it tomorrow if a customer bug then provide hot fix or patch etc http://qtp.blogspot.com
Priority 2 important may be a frequent failure of important functionality or service needs to be fixed ASAP, may be before the tester gets the next build/release http://qtp.blogspot.com
Priority 3 infrequent failure of important functionality or service there is a workaround and should be fixed latest by next release http://qtp.blogspot.com
Priority 4 cosmetic bug not affecting the functionality will be fixed when there is no other high priority work left for this application or module http://qtp.blogspot.com
These 4 severities/priorities are not carved in stone. There can be cases when there is a crash or an exception in an application. Also there are few spelling mistakes in menu names etc. That crash/exception is rare or for example occurs after following lengthy steps. So, for some, the spelling mistakes is a high priority bug from selling point of view and the crash/exception can be a high severity bug with low priority. http://qtp.blogspot.com
How to write a good bug report? http://qtp.blogspot.com
Steps to reproduce, What you expected to see, What you saw instead (actual). http://qtp.blogspot.com
Example of a bug report Bug Title: Entering new information and clicking save crashes the application. Area Path: Sprint 12working_with_users Build Number: XX_AV_1.2290 Test Type: Regression testing Changeset: 6302 Severity: 2 - Critical Priority: 2 Assigned to: Developer Name Reported By: Tester Name Reported Date/Time: 15.8.2013 14:20:45 Reason: Defect State: New/Open/Active Environment: Mac OS X 10.6 Description: Application crashes on clicking the SAVE after entering mandatory information. Steps To Reproduce: 1) Log into the Application. 2) Navigate to Module X. 3) Click New Form button and enter all the mandatory fields. 4) Click on Save button. Expected: there is an unhandled exception. Actual: there should not be any exception and the information entered should be saved. http://qtp.blogspot.com
Examples of bug reporting page of popular tracking tools http://qtp.blogspot.com
Apache Bloodhound http://qtp.blogspot.com
MS TFS http://qtp.blogspot.com
Finding bugs, categorizing bugs and writing good bug reports. Browse Browse. Interests. ... Finding bugs, categorizing bugs and writing good bug reports.
Finding bugs or rather finding critical bugs, categorizing bugs and writing good bug reports
You may also like. Finding bugs or rather finding critical bugs, categorizing bugs and writing good bug reports; How to write a good bug report; Microsoft ...
Writing a good bug report is very necessary in order to get your bug resolved. ... Here is the sample bug report for above mentioned ... of bug reports.
Categorizing bug reports is a technique that ... out what makes a good bug ... introduces bias in bug prediction models, confusing bugs and ...
... bug reports provide crucial ... C. Weiss, R. Premraj, and T. Zimmermann. What makes a good bug ... Bug writing guidelines. https://bugs.eclipse.org ...
Bug Reports. Articles, experts, jobs, and more: get all the professional insights you need on LinkedIn. ... Owner at Superior Bed Bug Solutions Past
How to find a bug, exploit it and write your own 0day exploit. In order to think like a hacker, ...