You will be disappointed, rather irritated when your submitted defects got rejected by developers. Your appraisal will get affected if your Defect Rejection Ratio is high, your team lead forgets to nominate your name for the award or reward program, and even you might land in facing crucial situation from your clients/manager. How to address this issue and increase your defects injection ratio rather increasing the defect rejection ratio. In this blog post, we will see what are the factors that you need to follow to address the situation.
Pre-requisite is to identify the defects and its details; then categorizing and prioritizing the defects. Following below steps on how to submit valid defects :
1. Search in existing defects database
HP Quality Center or Bugzilla is the most favorite defect tracking software that I have worked on. Trigger a search in QC/Bugzilla/Excel sheet or whatever the defect management tool that you are using and find whether already your defect has been submitted by you or your peer. This is the first and important check you need to validate, else developer just change the status from Submitted to DUPLICATE.
2. Reproducible or not
Once you identified the defect, try to reproduce the defect again and again. Some of the defect which I identified during mu initial stint, I was not able to reproduce due to browser compatibility, timeout error due to unstable environment (just for examples). If it is reproducible, then perform next check.
3. In-Scope or Out-of-Scope
Once the defect is reproducible, check whether the identified defect is in-scope i.e. whether that scenario/functionality is mentioned in Test Strategy/Plan. E.g. Payment Gateway scenario might in out-of-scope, since it is completely third party installment or CAPTCHA scenario. If it is in-scope, then perform following check, else forget about the defect submission.
4. Validate the test steps and data
Next step is to validate the test steps and test data. Check whether you are following right and sequential test steps and test data for the defects. You might’ve missed one or two steps or you might’ve used in-appropriate or invalid test data for testing. Make sure you fulfilled all the prerequisites or pre-conditions for the scenario. If you 100 per cent sure, then validate the following checks.
5. Test Environment
Are you testing in correct test environment with valid credentials? Are you using appropriate browser and its version? Are you working on correct OS and the service packs? Is your defect presents in the external interfaces? Is that external interface in-scope? If your answer is yes, then proceed further.
6. Record the test log
Most of the developers will say, “I am not able to reproduce the defects” or “It is working fine in my system”. To address this response, record all the test steps clearly with Microsoft Problems Steps Recorder or any other software or you can make a video, then share your desktop with the developer and show him about the defects.
If you follow above strategy, you can defend the defect rejections. I might have missed few points, please comment below, so that everyone can make a note of it.
Do you know something? QAInsights offering A BIG GIVE AWAY. Participate and Win surprise gifts 🙂
Thanks for visiting QAInsights! Check out our new portal Testifications.com to get updates on Software Testing related certifications. We’re always posting interesting articles on QAInsights. I request you to subscribe so you don’t miss out anything.
Searching for QA Jobs Openings, check it at www.QAJobOpenings.com
Want to start a blog like this, please visit SpidyDomain to buy cheap web hosting and register domain.
Image courtesy of Stuart Miles at FreeDigitalPhotos.net
- Measuring Client-side performance using Performance APIs - September 19, 2017
- Unboxing HPE LoadRunner 12.55 - August 20, 2017
- Measure Client-side Performance using Lighthouse - August 10, 2017
- Perf Calculator – free iOS app for performance testers - July 16, 2017
- How to performance test AngularJS or ReactJS applications? - June 25, 2017