Priority and Severity

What is Priority and Severity in Testing?

Equivalence partitioning and Boundary Value Analysis.

Password field is there,we can accepts every character except underscore and semicolon. It can accept min 6 characters and maximum 12 characters. Prepare boundary value and equivalence class test case 

Question  by Mudaseer Ahmed

We will understand what is Equivalence partitioning and Boundary Value analysis.  

Equivalence partitioning : is a testing technique where input values required for testing are grouped into two classes

1. Valid Inputs  Class: Class which holds all the valid inputs.

2.Invalid Inputs Class: Class which holds all the Invalid inputs

Eg;  To Check the Password which can accept all the characters except underscore("_") and Semicolon(";")

and which accepts characters length 6 and maximum 12. 

We Define a Equivalence classes

Now to perform positive testing, Consider set of values from class EC1,When the password is entered "Password is accepted"

To perform Negative Testing choose the values from class EC2 and EC3, When the password is entered from these classes "Password shall not be accepted by the System"

Boundary Value analysis : Is a testing technique , where values for testing are chosen from the class which falls within different boundries

Eg; To test the password field which accepts minimum of 6 characters and Maximum of 12 Characters. 

We will define the boundary of each class of Inputs

To satisfy Boundary value, tester will have to write Test Cases considering values from  Valid region and each Invalid Region and Values which define exact boundary.

For our example we require 5 Test Cases

1. Consider password length less than 6

2. Consider password of length exactly 6

3. Consider password of length between 7 and 11

4. Consider password of length exactly 12

5. Consider password of length more than 12 

Note : 1st and 5th Test Cases are considered for Negative Testing

Sanity Testing and Smoke Testing

What is Sanity Testing and Smoke Testing?

Smoke Testing : Test Scripts are generated in such a way that crucial functional parts of the System are covered. Here Tester is trying to cover major functionalities that are suppose to work fine.Usually before the release of any prodcut Smoke Test is conducted to ensure crucial functionalities are working as they suppose to function. 

Sanity Testing: Sanity Test is  in depth Regression, Test may be conducted at the very low level. Usually script is not written for Sanity Test.

ReTest and Regression Testing

What is  the difference between Retesting and Regression Testing?


ReTesting :  is testing the functionality which is already tested. 
  
eg;- We test "Book Withdrawal Functionality of Library". if  Tester  finds a defect  in the functionality he will raise a defect. Once the developers fixes the issue. Tester is Retesting the same functionality. 


Regression Testing : When any changes occur in the existing system Tester tests the new functionality and  also tests  how the new changes are getting effected with the already existing functionality. 


eg:- If the Withdrawal functionality of the Library system is updated to support withdrawal for outside users. 
Here Tester is testing working of withdrawal functionality of Out Side users and also Testing existing User to validate already existing functionality are working as required.