Best Practices for Quality Bug Hunting

QA engineers monitor every phase of the software development process to ensure design quality, making sure that the software meets the standards set by the development company and the client where the client expect for a ‘Defect Free Product’

Defect Free Product is a myth – It is important for test team to understand that a 100% defect free product delivery is far from reality. Testers need to align their work with this fact. They could always be passed as a condition and be fixed at a later time.

QA engineers not only check the product, also test the product.

Checking is not testing but Testing is the combination of Checking and Exploring (Testing = Checking + Exploring)

Important Goals of Software Testing:

1. Always Identifying the bugs as early as possible.

2. Preventing the bugs in a product.

3. Check whether the customer requirements criterion is met or not.

4. And finally main goal of testing to measure the quality of the product.

Best practices for Quality Bug Hunting:

Bug is a mismatch between expected result and actual result. 

Spend some time in understanding application logic. Once logic is clear, finding bugs will be easier. QA should be curious to find the bugs.

Understand the application functionality and prepare a checklist of test cases accordingly. Then start your testing. As a tester, when you detect the bug you have to report it.

Reporting a Bug

Validate your bugs: Before submitting a bug, validate it thoroughly and make sure that it is reproducible every time.

Detailed submission: A clear and easy to understand submission definitely helps the program owner in investigating and fixing the issue faster.

When submitting a bug, it is important to provide proper analysis and recommendations to report the bug. Without proper analysis provided, even a real bug can be treated as a not-valid.

A detailed submission generally includes:

·         >> Easy to understand description of the bug

·        >>  Location of the bug and detailed steps to reproduce it

·         >> Explanation of how it impacts the product

·         >> Browser/Platform version

·         >> Proof of concept code/image/video

QA Artifacts:

·         -> Test Plan

·         -> Test Scenarios

·         -> Test Cases

·         -> Test Steps

·         -> Test Data

·         -> Test Estimation

·         -> Test Schedule

“Discovering the unexpected is more important than confirming the known.”

Proud to be a QA