Test cases Strategy

rose · #1 (**permalink**) 12-13-2006

Hi

Its a simple question regarding the testcase
What should be the strategy followed for writing the testcases??
a.Writing all the functionalities...possibilities..scenarios we can think of...all cosmetic things(labels,taborder,,,)making the coverage 100%??

or

b.Following a general pattern which just covers the major functionality and then go about writing the testcases when we find bugs during bughunting

I wont ur opinion...On which is a better strategy??
on things like
1.which one saves time
2.Which one is fruitful??

Thanks in advance

sutnarcha · #2 (**permalink**) 12-18-2006

Different companies choose different approaches depending on their policies, strategies and more importantly their budgets.

My vote goes to ‘A’ as 100% quality is more important than anything else (cost/time).

rose · #3 (**permalink**) 12-18-2006

When workin against deadlines..we definitely needs to save time...
A is the approach i am following right now...But what made me think was
"If we can find bugs at the blink of an eye(blink testing by James bach)why should we waste our time in documenting so many testcases written for GUI specific things??".

We can better concentrate on N number of scenarios affecting our functionality of the application....So could upls explain to me..Which one is good...Or I need to go in both the ways??

schittoor · #4 (**permalink**) 12-19-2006

See Test case strategy means how u r going to test the application , first u can plan it and test it based on the test case before the plan, this is some companies follows different different ways, depending on the client.

Thanks
srinivasulu.chittoor

bvani · #5 (**permalink**) 02-12-2007

I vote for A.

but while we implement we would initially list all the possible test factors in the test strategy document. then during planning we would even consider the factors like time and cost and implement the related testing techiniques.

jainbrijesh · #6 (**permalink**) 03-01-2007

Tester should write testcase according to HLS and LLS.
This is the best approach and followed by MNC's.
It's also a metric to count the tester efficiency.

raghav.kamal · #7 (**permalink**) 03-01-2007

I would agree with Vani as she sounds to be absolutely correct

nkamuni_mca · #8 (**permalink**) 12-30-2008

Quote:

Originally Posted by sutnarcha

Different companies choose different approaches depending on their policies, strategies and more importantly their budgets.

My vote goes to ‘A’ as 100% quality is more important than anything else (cost/time).

I always go with A. As it gives u 100% testing of the product.

But as told by Sutnarcha, it is always the companies discussion which we have to follow.

Regards,
Narin Kamuni

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Uploading Test Cases into Quality Center and Test Director	Rajani	Test Director	2	05-13-2008 05:27 AM
Test cases for Push Button	Srikanth	Test Cases	7	05-16-2007 07:32 AM
test cases for Radio	neetisharma	Test Cases	4	04-18-2007 06:57 AM

The Following User Says Thank You to rose For This Useful Post:
venubyna

Test cases Strategy

Test cases Strategy

Similar Threads