What do you do if a defect is not reproducible?

First step: By using some sort of remote software, you let the customer tell you what to do to reproduce the problem on the system that has it. If this fails, then close it. Second step: Try to reproduce the problem on another system. If this fails, make an exact copy of the customers system.

How do you deal with inconsistent defects?

Inconsistent defect is one which is not a stable defect. These kind of defects won’t occur frequently. To handle these kind of defects, better to attach screenshots and clear steps to reproduce with test data while logging the defect to avoid unnecessary comments by other teams.

How do you check for defect leakage?

Defect Leakage is the metric which is used to identify the efficiency of the QA testing i.e., how many defects are missed/slipped during the QA testing. Defect Leakage = (No. of Defects found in UAT / No. of Defects found in QA testing.)

When developer will say defect is not reproducible?

If the bug is not reproducible, then the testing effort used in finding, analyzing and reporting that particular bug/defect is a total waste. For understanding and reproducing a bug, it is essential to have detailed and properly explained ‘Steps to Reproduce’, state and environment in which the bug occurred.

How do you convince the developer if the status is not reproducible?

If you cannot reproduce it, you cannot tell if it is fixed.

1. Consider the execution environment specific.
2. Consider the external service.
3. Check if the app produces log at either your device or some remote log collector.
4. Check the log of server components which your app work with.
5. Ask your dev mate for help.

What does it mean when a developer says that defect is not reproducible?

How do you reproduce a defect?

How to Reproduce a Defect?

1. Clear all junk files, including cache and cookies.
2. Observe every step carefully.
3. Look for similar defect or patterns.
4. Write each and every step, including test data, system settings, screenshots, server logs, and other factors.
5. Do not decide the occurrence of defect from a single instance.

What is a good defect leakage?

Generally, good testing processes have roughly a 90\% TEI, with only 10-12\% defect leakage. However, as stated above, QA Mentor aims higher than that for a 5\% defect leakage.

What is leaked defect?

What is Defect Leakage? After the delivery of application or product or we can say after the release, if end user or Customer find any defect by using that application then it is called defect leakage, it is also called bug leakage.

What is a defect in QA?

Definition: A defect is an error or a bug, in the application which is created. A programmer while designing and building the software can make mistakes or error. These mistakes or errors mean that there are flaws in the software. These are called defects.

What happens when a defect is rejected by a developer?

A developer should start analyzing and fixing the defect at this stage. When the developer feels that the defect is not genuine or valid, then the developer rejects the defect. The status of the defect is marked as “ Rejected ” and assigned back to the testing team.

What is the difference between “known defect” and “fixed defect”?

If a defect is already known and currently present in the production environment then the defect is marked as “ Known defect ”. When a developer makes the necessary changes, then the defect is marked as “ Fixed ”. The developer now passes the defect to the testing team to verify, so the developer changes the status as “ Ready for Retest ”.

Can a tester report a defect to a developer?

As a tester point of view we can give enough evidence regarding that defects .for example we can take screen shot of that defects and attach to bug reporting sheet. Generally tester report to their Test lead or Manager ..not to developer . Tester will not argue anything with developer to proof.

What is the difference between defecttester and project manager?

Tester finds the defect. Status assigned to defect- New. A defect is forwarded to Project Manager for analyze. Project Manager decides whether a defect is valid. Here the defect is not valid- a status is given “Rejected.”. So, project manager assigns a status rejected.