# Thread: Equivalence Partitioning & Boundary Value analysis

1. ## Equivalence Partitioning & Boundary Value analysis

Hi All,

How we can differentiate "Equivalence Partitioning" & "Boundary value analysis" ?

2. ## Re: Equivalence Partitioning & Boundary Value analysis

Equivalence Partitioning, I think, is eliminating certain test cases because they are, in someway, redundant. For example, testing both winME and winXP are *sometimes* considered redundant executions.

Boundary value analysis is finding the outside values for a test case. An example of this is testing not just the date 1900, but testing 1901 and 1899.

This is general stuff I've learned in the field, it may be up for debate.

3. ## Re: Equivalence Partitioning & Boundary Value analysis

If you break-up all possible inputs in the example above into "1900", "less than 1900", and "greater than 1900", you are using equivalence partitioning to conduct boundary value analysis. These three groups are internally equivalent -- there is no difference to the test if you use 653 or 1898, they are equivalent within the "less than 1900" partition.

Hope that helps.

4. ## Re: Equivalence Partitioning & Boundary Value analysis

Equivalence Partitioning:
A class of homogenous inputs which are similar in nature to the extent that they result in similar outputs. If one element is tested successfully then it would represent the entire class

Boundary Value Analysis:
Testing the input values at their boundaries (keeping the requirement in mind)

5. ## Re: Equivalence Partitioning & Boundary Value analysis

I can tell you more about BVA technique.
BVA- in order to test some value which has min and max we have to perform:
1.min-1
2.min
3.between max & min
4.max
5. max+1
So, if you have range in requirement for edit box
5-25 an- you will create test w/five steps.
If req.: 25 char--> 4 steps( you can't check min-1)

6. ## Re: Equivalence Partitioning & Boundary Value analysis

Originally posted by koshlu:
I can tell you more about BVA technique.
BVA- in order to test some value which has min and max we have to perform:
1.min-1
2.min
3.between max & min
4.max
5. max+1
So, if you have range in requirement for edit box
5-25 an- you will create test w/five steps.
If req.: 25 char--> 4 steps( you can't check min-1)
<font size="2" face="Verdana, Arial, Helvetica">So basically spelt out the test would be
BVD for range 5 - 25

4, 5, 15, 25, 26

No more no less [img]images/icons/smile.gif[/img]

7. ## Re: Equivalence Partitioning & Boundary Value analysis

hi all,
Equivalence partitioning is a black-box testing method that divides the input domain of a program
into classes of data from which test cases can be
derived.

Boundary value Analysis
These leads to a selection of test cases that exercise bounding values.
eg.
If an input condition specifies a range bounded by value a and b, test cases should be designed with values a and b just above and just below a and b respectively.

8. ## Re: Equivalence Partitioning & Boundary Value analysis

dear all
both of them are coverage based techniques which focus on what gets tested.

Equivalence partitioning or Equivalence class analysis is a set of values for a variable that you consider equivalent.test cases are equivalent if you believe that (a)they all test the same thing;(b)if one of them catches a bug,the other probably will too;and(c)if one of them doesn't catch a bug,the others probably won't either.once you've found an equivalence class,test only one or two of its member.

9. ## Re: Equivalence Partitioning & Boundary Value analysis

Equivalence partitioning: a formalization of a reasonably intuitive concept, reduce the number of test cases you need to cover by eliminating redundant cases. Can be described in terms of path testing as defining all input value cases that exercise the same path.

Boundary value analysis: an exercise in determining the specifics for focussing bug hunting on one very common problem area.

10. ## Re: Equivalence Partitioning & Boundary Value analysis

Originally posted by koshlu:
I can tell you more about BVA technique.
BVA- in order to test some value which has min and max we have to perform:
1.min-1
2.min
3.between max & min
4.max
5. max+1
So, if you have range in requirement for edit box
5-25 an- you will create test w/five steps.
If req.: 25 char--> 4 steps( you can't check min-1)

Does BVA completely assures that performing test for 4, 5, 15, 25, 26 values will completely avoid the failure of the test case?

It may fails for values like: 6 or 11 or 13.
So how do we recognise these values?what to do in such case?

Page 1 of 2 12 Last

#### Posting Permissions

• You may not post new threads
• You may not post replies
• You may not post attachments
• You may not edit your posts
•

vBulletin Optimisation provided by vB Optimise v2.6.0 Beta 4 (Pro) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.