Thanks:  0
Likes:  0
Dislikes:  0

# Thread: Regarding Equivalence class partioning

1. ## Regarding Equivalence class partioning

Hi All,

But I would like to know why are they called as Equivalence Classes?

2. ## Re: Regarding Equivalence class partioning

Because all elements of the same equivalence class should show the same behaviour - each element should be equivalent to each other.

Regards,
Juergen

Hi Bru,

Thanks...

4. ## Re: Regarding Equivalence class partioning

In Equivalence class partioning the range of data is equally divided in to parts and then BVA technique is performed on the same for 100% coverage.

-Sandeep

5. ## Re: Regarding Equivalence class partioning

Wow...simply equally dividing a range of data into parts and then boundary testing to get 100% coverage! Sorry, but this is (perhaps) the most rediculous thing I have ever heard.

So...let's get back to reality.

GeeVee, a good explaination of why they are called equivalence classes can be found here http://www.iscid.org/encyclopedia/Equivalence_Relation

Also, take a look at my article that gives a introduction to the technique here http://www.stpmag.com/issues/stp-2007-10.pdf

6. ## Re: Regarding Equivalence class partioning

I agree with bru...

7. ## Re: Regarding Equivalence class partioning

I agree with BJ on this. Even with equivalence class partitioning and boundary testing, you are not 100% coverage. This may conclude the data-driven testing that you have defined, but it is ceratinly not 100% coverage.

I would argue that it isn't even 100% coverage for data-driven testing. Unfortunately, any number in a given input field may generate an error. Therefore, if you do not test every single input that could be possible for that field, there is still the risk of an error.

This is where using exploratory testing techniques in conjunction with your equivalence partitions and boundary testing can help to produce some unexpected results also. However, if you are able to automate that input field, then you should be able to get more iterations running through that field and get closer to a full coverage.

Unfortunately there will almost always be an infinite number of inputs that can be entered into a field. Especially a text field. So just make sure that you have documented the necessary testing you are performing and if that amount of testing is acceptable to your management, then that should be good.

8. ## Re: Regarding Equivalence class partioning

In order to reach 100% coverage, you need to use a different technique. BVA en ECP can not even provide a measurable coverage.

9. ## Re: Regarding Equivalence class partioning

Are we speaking here about the code coverage, requirements coverage or functional coverage?

10. ## Re: Regarding Equivalence class partioning

I didn't think we were refering to coverage at all; we were discussing the technique of equivalence class partitioning. Equivalence class partitioning is a functional testing technique designed to evaluate the functional capabilities or attributes of a specific input or output parameter through a detailed analysis of the variable data for that parameter.

So, the application of the technique may apply to functional coverage, it may affect code coverage (or not) and it may affect requirements coverage (or not).

When a specific technique is taken out of context and basterdize its usage by attempting to apply it to other types of testing then the value of that technique diminishes rapidly.

#### Posting Permissions

• You may not post new threads
• You may not post replies
• You may not post attachments
• You may not edit your posts
•
Search Engine Optimisation provided by DragonByte SEO v2.0.36 (Pro) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.