Thanks:  0
Likes:  0
Dislikes:  0

# Thread: counting conditions vs verifications

1. ## counting conditions vs verifications

there had been a long debate in our group as to count conditions or verifications in our test plan for our test cases.

verifications are expected results, by the way.

for example,

a condition is: a user clicks the button
a expected result is: a window pops up

above is a simple example but there are times when you have multiple verifications with one condition or multiple conditions.

can any one throw some light on to what to count? is it the conditions or verifications? I feel it needs to be test conditions not the verifications.

anyone?

2. ## Re: counting conditions vs verifications

Are you saying that "count" is to tally the number of conditions or verifications, or that "count" means that something matters or counts toward the result? Once that is cleared up, we can proceed to the actual question, which I believe is: "it doesn't matter".

3. ## Re: counting conditions vs verifications

[ QUOTE ]
can any one throw some light on to what to count?

[/ QUOTE ]

You should only count the items where the total gives you meaningful information.

If there's meaning to the "total number of conditions", then count them.
If there's meaning to the "total number of verifications", then count them.

4. ## Re: counting conditions vs verifications

sorry, when i meant count i meant the total # of conidtions or verifications

5. ## Re: counting conditions vs verifications

Basically the same question - why do you want the total number of these - what do you expect to use them for?

6. ## Re: counting conditions vs verifications

What is the purpose of counting either one of those? For figuring out how to portion out test scripts to testers?

For that our test strategy indicates to portion them out by weight (in ounces).

7. ## Re: counting conditions vs verifications

So, you portion by the weight of the ink on the paper then? Very , VERY, strange.

8. ## Re: counting conditions vs verifications

[ QUOTE ]
So, you portion by the weight of the ink on the paper then? Very , VERY, strange.

[/ QUOTE ]

No, by the weight of the reams on reams of paper.

9. ## Re: counting conditions vs verifications

ok all, the purpose of counting the conditions or verifications is to get the total # of conditions executed for the test plan for that project.

10. ## Re: counting conditions vs verifications

no one hear in our company atleast in our QA organization uses a test strategy. as strange as it sounds this is afortune 500 company....go figure...however i do a test strategy for all my projects...

#### 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.