Purpose of Equivalence Partitioning in testing
https://www.zyxware.com/sites/default/files/styles/user_image/public/default_images/index.png?itok=2YmREnrP
BY tiju.thomas
5 years ago
Testing
0 comments comment

As test case is the important document for testing, testers use different effective techniques for preparing the same. Equivalence Partitioning or equivalence classes is one of the effective techniques among them. It is a black box testing technique, which focusses mainly on the functionality of a software. Therefore the main aim of equivalence partitioning is to prepare an effective test case which covers the total functionality of an application. In this article, I have included a brief note on Equivalence Partitioning.

Equivalence Partitioning is a software testing technique that allows the tester to divide the input domain into different partitions of classes, i.e. divides the inputs as valid and invalid classes. It uncovers the classes of errors.

For example; Consider if the Input Domain for a Text Field in a site is 1 to 1000. So while preparing test cases there is no use for writing number of test cases for all valid input datas and other test cases for invalid datas. By applying 'Equivalence Partitioning' the testers will divide this Input Domain into 3 classes of inputs :

  • Any value less than 1 ( Invalid )
  • Any value within 1 to 1000 ( Valid )
  • Any value greater than 1000 ( Invalid )

Any value within each class of inputs satisfies a particular test case, it is assumed that all the values within those classes will satisfy the test case.

The advantage of 'Equivalence Partitioning' is, it allows the testers to reduce the number of test cases, also it reduces the testing time of a software because of lesser number of test cases. If you have additional points, use the below comment box. Happy testing..


RELATED ARTICLE

/themes/custom/zyxpro_light/images/placeholder.png
close

on 30th May 2012 / by anju.r
A software bug is defined as an error or failure or fault in a system or computer program that produces an unexpected or incorrect result. This is applicable for any Drupal/non-Drupal website. The bug life cycle in a Drupal website consists of steps from identification to closure of a bug. Different stages of Bug Life Cycle are: Testing Bug life cycle Leave a reply Your email address will not be published. Required fields are marked *
/themes/custom/zyxpro_light/images/placeholder.png
close

on 21st June 2012 / by tany.antony
Software Testing is the process carried out during software development, so as to ensure and verify that the product, be it a simple program or an entire Drupal site, developed has all the desired features, performs as expected by the customers and meets all their requirements. It also the ensures the robustness of the product. Here is the Levels of Testing in a Drupal Development Workflow. Testing Levels of Testing Leave a reply Your email address will not be published. Required fields are marked *
Leave a reply
Your email address will not be published. Required fields are marked *

Filtered HTML

  • Web page addresses and email addresses turn into links automatically.
  • Allowed HTML tags: <a href hreflang> <em> <strong> <cite> <blockquote cite> <code> <ul type> <ol start type='1 A I'> <li> <dl> <dt> <dd> <h2 id='jump-*'> <h3 id> <h4 id> <h5 id> <h6 id>
  • Lines and paragraphs break automatically.
The content of this field is kept private and will not be shown publicly.
CAPTCHA This question is for testing whether or not you are a human visitor and to prevent automated spam submissions.