The QA team starts testing a software/product and there are “way too many” defects. Every other scenario is failing, new flows are explored & clarifications sought. What would be the strategy now?
Many a times we face these kind of one-off bugs 🙁 which peep-out and then hide somewhere. “It was a one-off bug and now not reproducible – so what can I do?” Wrong! Though one-off but still it is present somewhere in the software and as a Tester it is our responsibility to investigate it. How?
Defect Leakage is natural. It’s common. If you build a software, bugs will be there. Similarly even if you Test a software, you cannot prove their absence. But we can do our best to eliminate maximum of them. Typically in most of the projects even if you complete functional testing (system testing) without any time & cost constraints, still UAT team (Business) manages to catch some more bugs. Any idea why? There has to be something missing in the system test coverage. What is it?
In software testing, it is most important to measure the quality, cost and effectiveness of the project and the processes. Without measuring these, project can’t be completed successfully. The goal of testing is to determine if the requirements are met. During the course of testing, we find defects, or instances where the software does not meet requirements. Hence, in the area of software testing metrics, there has been abundant work in analyzing defects via different Defect metrics.
The most important yet confused concept – Defect Severity and Priority. Additionally it is one of the most popular Software Testing interview question.
Emails and Excel are not enough to manage defects in a large project. For single source of truth and maintain consistency, we need a Bug Tracking Software.
Everything has a lifecycle – it’s the law of nature, a series of changes in form that an organism undergoes, returning to the starting state. Birth >> Infancy >> Childhood >> Teenage >> Adult >> Mature >> Old age >> Dead end. A ‘Defect’ in Software Testing also follows a pre-defined stage transitions from its identification till its closure. In Software Testing terms, we call it as ‘Defect Status transition’ or a ‘Defect Lifecycle’!