Saturday 6 August 2022

How to prioritise the test cases for QA and Automation? How to prioritise test cases for regression testing?


SDET Interview Question and Answers

TestNG Interview questions and answers

Jenkins Interview Questions and Answers

Appium Interview Questions and Answers

Selenium Interview Questions and answers

Java Coding Interview Questions and Answers

GIT Interview Questions and Answers

Description

The document provides guidelines on how to define priorities for test cases. Note that application and firmware approaches when defining priority may be different, but the general approach should stay common. 

Priorities should be set in regards to the regression suite, meaning that the reporter should work on the test case as if it's part of the regression suite and consider the priority for the whole app and not for the feature itself. 

Priority should be defined according to the feature importance and its impact on the other application features. For example, the test case has priority P1 in comparison to other feature cases, but in comparison to other cases in-app (in regression suite), it gets P2 priority. So the initial priority should be set to P2.

While setting the priority during feature testing, the reporter should stick to the following distribution:

  • P0 - 10%
  • P1 - 25%
  • P2 - 45%
  • P3 - 15%
  • P4 - 5% 

With 5% deviation for P2, P3, P4

Priority guidelines (application)

Priority
Description
Examples
P0

Results of test failures are bugs with BLOCKER priority

Tests cover critical user flows and the most popular user scenarios.

Functionality is a blocker to proceed with the rest of the test cases related to this feature  

Login flow


P1

Results of test failures most likely lead to bugs with CRITICAL priority 

Basic user scenarios work with noticeable errors

Basic scenarios for a specific device or device configuration

Setup with specific conditions

Some functionality is available for shared users


P2

Results of test failures either lead to bugs with MAJOR priority but in certain scenarios (a group of cases) can lead to CRITICAL bug

Incorrect notifications or labels in noticeable areas

Incorrect behavior in complex user flow that can be avoided

User actions that do not break app functionality

Reliability of applications in case of non-normal user behavior 

Action Button Design and Status


P3-P4

Results of test failures lead to NORMAL/MINOR bug creation

Specific localization cases

Minor and not popular user flows the don't affect any major functionality

Live view minor issues


Emails with spaces



************************************************

✍️AUTHORLinkedIn Profile

************************************************

Learn (API-Microservice)Testing+ Selenium UI Automation-SDET with Self Paced Videos prepared by FAANG employee and LIVE Doubt Session 

SDET TRANING VIDEOS AVAILABLE with Live Doubt Session(course-1 below,API TRaining Videos With Class Notes and Coding Set) and (API+UI, both course-1 & 2 below) Check Training Page for Course Content or reach out @whatsapp +91-9619094122. 
This includes classnotes, 300+ interview questions, 3 projects, Java Coding question set for product companies along with career guidance from FAANG employee for Automation and SDET.

For more details whatsapp 

Check below link for question and answers with the code:

Top API Interview Question 1-10

Top API INterview Questions 11-20 

Top API AUTOMATION Interview Q&A - 21-30

*************************************************

SeleniumWebdriver Automation Testing Interview Questions:

https://automationreinvented.blogspot.com/search/label/SeleniumWebdriver

API Testing Interview Question Set:

https://automationreinvented.blogspot.com/search/label/Rest-API

Kubernetes Interview Question Set

https://automationreinvented.blogspot.com/search/label/Kubernetes

Docker Interview Question Set

https://automationreinvented.blogspot.com/2020/02/top-18-docker-commands-for-aytomation.html

Linux Interview question Set

https://automationreinvented.blogspot.com/search/label/Linux

Automation Testing/SDET Framework Design

https://automationreinvented.blogspot.com/search/label/FrameworkDesign

Java Related Interview Question Set

https://automationreinvented.blogspot.com/search/label/Java

GIT Interview Question Set:

https://automationreinvented.blogspot.com/search/label/GIT

Coding Interview Question Set:

https://automationreinvented.blogspot.com/search/label/Coding%20Questions

Mobile Testing Interview Question Set:

https://automationreinvented.blogspot.com/search/label/Mobile%20Testing

Python Interview Question Set for QAE - SDET - SDE:

https://automationreinvented.blogspot.com/search/label/Python


Linux Interview question Set
https://automationreinvented.blogspot.com/search/label/Linux

 
Automation Testing/SDET Framework Design
https://automationreinvented.blogspot.com/search/label/FrameworkDesign


Java Related Interview Question Set

https://automationreinvented.blogspot.com/search/label/Java


GIT Interview Question Set:
https://automationreinvented.blogspot.com/search/label/GIT


Coding Interview Question Set:
https://automationreinvented.blogspot.com/search/label/Coding%20Questions
Mobile Testing Interview Question Set:
https://automationreinvented.blogspot.com/search/label/Mobile%20Testing

Python Interview Question Set for QAE - SDET - SDE:
https://automationreinvented.blogspot.com/search/label/Python

No comments:

Post a Comment

All Time Popular Posts

Most Featured Post

Introduction to Web Testing with Playwright

  Introduction to Web Testing with Playwright 📌  Telegram Group:  https://t.me/+FTf_NPb--GQ2ODhl 📌  YouTube channel:  https://lnkd.in/gGUG...