Testplace tutorials
  • Quality Assurance 101
  • Manual Testing
    • Manual Testing Tutorial
      • What is Software Testing?
      • Software Development Life Cycle
      • Software Testing Life Cycle
      • Types of Software Testing
      • Levels of Testing
      • Automation Vs Manual Testing
      • Black Box & White Box Testing
      • Smoke & Sanity Testing
      • Regression Testing
      • Retesting
      • Regression vs Retesting
      • Entry And Exit Criteria
      • Test Scenario vs Test Case
      • Manual Testing Methods
      • Verification and Validation
      • Test Strategy
      • Test Plan
      • Test Strategy vs Test Plan
      • Bug Report Template
      • Test metrics
      • Difference Between Defect Bug Error And Failure
      • Write Good Bug Report
      • Principles of Software Testing
      • Black Box Test Design Techniques
      • Equivalence Partitioning Testing Technique
      • Boundary Value Analysis Testing Technique
      • Decision Table Test Design Technique
      • State Transition Test Design Technique
      • Severity Vs Priority
Powered by GitBook
On this page

Was this helpful?

  1. Manual Testing
  2. Manual Testing Tutorial

Equivalence Partitioning Testing Technique

PreviousBlack Box Test Design TechniquesNextBoundary Value Analysis Testing Technique

Last updated 5 years ago

Was this helpful?

Equivalence Partitioning is also known as Equivalence Class Partitioning. In equivalence partitioning, inputs to the software or system are divided into groups that are expected to exhibit similar behavior, so they are likely to be proposed in the same way. Hence selecting one input from each group to design the test cases.

Each and every condition of particular partition (group) works as same as other. If a condition in a partition is valid, other conditions are valid too. If a condition in a partition is invalid, other conditions are invalid too.

It helps to reduce the total number of test cases from infinite to finite. The selected test cases from these groups ensure coverage of all possible scenarios.

Equivalence partitioning is applicable at all levels of testing.

Example on Equivalence Partitioning Test Case Design Technique:

Example 1:

Assume, we have to test a field which accepts Age 18 – 56

Valid Input: 18 – 56

Invalid Input: less than or equal to 17 (<=17), greater than or equal to 57 (>=57)

Valid Class: 18 – 56 = Pick any one input test data from 18 – 56

Invalid Class 1: <=17 = Pick any one input test data less than or equal to 17

Invalid Class 2: >=57 = Pick any one input test data greater than or equal to 57

We have one valid and two invalid conditions here.

Example 2:

Assume, we have to test a filed which accepts a Mobile Number of ten digits.

Valid input: 10 digits

Invalid Input: 9 digits, 11 digits

Valid Class: Enter 10 digit mobile number = 9876543210

Invalid Class Enter mobile number which has less than 10 digits = 987654321

Invalid Class Enter mobile number which has more than 11 digits = 98765432109