How To Make Use Of Stats For Post-Release Bugs

Lecture 2 - The Purpose of Testing -> Quick Intro -> Exposing Misconceptions -> How To Make Use Of Stats For Post-Release Bugs -> Testing And QA

BTW

Each bug has a priority which reflects that bug’s importance for business of the company. Priorities usually range from P1 to P4, with P1 being the most critical: if user cannot register, it’s P1; if some link has navy color instead of blue color, it’s probably P4.

Here is the idea: After each release, post-release bugs are analyzed for the purpose of finding weak link(s) in the software development process.

You should have QATUTOR Membership to view this page. Please, login or sign up. If you are already logged in, try refreshing this page.
Lecture 2 - The Purpose of Testing -> Quick Intro -> Exposing Misconceptions -> How To Make Use Of Stats For Post-Release Bugs -> Testing And QA