Software testing-defects and examples

Retesting is a planned testing. We do use same test cases with same test data which we used in the earlier build. If you liked this video, then please subscribe to our YouTube Channel for more video tutorials. When there is a particular bug fix specified in the Release Note: Once the development team releases the new build, then the test team has to test the already posted bugs to make sure that the bugs are fixed or not.

When a Bug is rejected: At times, development team refuses few bugs which were raised by the testers and mention the status of the bug as Not Reproducible. In this case, the testers need to retest the same issue to let the developers know that the issue is valid and reproducible. To avoid this scenario, we need to write a good bug report. Here is a post on how to write a good bug report. When a Client calls for a retesting: At times, the Client may request us to do the test again to gain the confidence on the quality of the product.

In this case, test teams do test the product again. A product should never be released after modification has been done to the code with just retesting the bug fixes, we need to do Regression Testing too. Also Read: Difference between Regression and Re-testing. Check this out for Complete Manual Testing Tutorial. Test Management. Smart Impact Analysis. Explore the platform.

Customer Experience Our organization dedicated to ensuring, accelerating, and scaling your success. Customer Success From onboarding to advocacy and enablement, our Customer Success Management team is there for account support and strategic guidance.

See all resources. Insights for CIOs. Get Tricentis certified. Start your learning journey. Your transformation toolkit. Search Tricentis. Solutions By enterprise apps By industry.

Back Tricentis advantage Speed Savings Customer stories. Company Management team Careers Locations. Performance Testing Tricentis NeoLoad. Test Management Tricentis qTest. Customer Experience. Consulting Services. Customer Success. Latent defects are among those important defects that are present in the software and can impact its functionality over time.

Therefore, it is crucial for the team of testers to take all the necessary measures to ensure they are identified and resolved before the product is delivered to the end-user. We deliver. Get the best of Professional QA in your inbox. Toggle navigation. Home Contact Us About Us. Give your feedback! Get New Content Update. Popular Posts. Data Flow Testing.