Dis Adv of over testing?

priyanka · 16-02-06, 05:30 AM

hai friends
1.What are the disadvantages of overtesting?
2.What happens to the test plan if the application has a functionality not mentioned in the requirements?
can u give the answer plzzzz

**sowmya571** · 16-02-06, 12:52 PM

hello priya

will get back to u soon ya

bye

sowmya

**sk_kireeti** · 28-02-06, 02:59 AM

Hi Priyanka,

1.What are the disadvantages of overtesting?

Overtesting an applicationmean,trying to test each and every possible combination of functional flowswhich is never possible in this ideal world.

Most of the customers may not use all the features of the application(especailly if it is product rather being project)and thus wewill wasting our resources unnecessarily on those low priority aspects of the product. Rather spending time onthese low priority features, if we concentrate on high priority/most frequently used features, that may yeild high productivity. Again, a point to stress here is, it is never possible to release a bug free application. But, by testing we can only minimize the cost of the bugs.

2.What happens to the test plan if the application has a functionality not mentioned in the requirements?

It clearly represents the communication gap between PM(Project Management)/Dev team and QA teams.

In case of such situations, first try to understand the new functionality that is added ( by contacting dev or PM POC's) and then know what is the business requirement for it and get ajustification from them.Then QA should be able to guess what will be its impact on the over all functionality. If it impacts the functionality or changes the complete functionality, then the QA should modify their scripts accordingly. If the new functionality does not have any impact on the functinality then there won't be any chages. But, in real time, the situation will be, we have to uplift our scripts covering the new features.

If you have any more doubts or if I am not clear on any aspect, please let me know.

Thanks,

Krishna

AjayKumar.Kataram · 08-12-08, 11:14 PM

Good one....

aforarun · 10-12-08, 05:19 PM

Thanks Kireeti... Good info..

antojap20 · 10-12-08, 07:15 PM

Good Info

16-02-06, 05:30 AM	#1 (permalink)
priyanka Junior Member Join Date: Feb 2006 Location: India Posts: 9 Thanks: 0 Thanked 0 Times in 0 Posts Rep Power: 4	hai friends 1.What are the disadvantages of overtesting? 2.What happens to the test plan if the application has a functionality not mentioned in the requirements? can u give the answer plzzzz
Offline

16-02-06, 12:52 PM	#2 (permalink)
sowmya571 Moderator Join Date: Feb 2006 Posts: 1,413 Thanks: 0 Thanked 17 Times in 14 Posts Rep Power: 20	hello priya will get back to u soon ya bye sowmya __________________ http://livetolead.blogspot.com/ all the best Arise Awake N Stop Not Until Ur Goal Is Reached!
Offline

28-02-06, 02:59 AM	#3 (permalink)
sk_kireeti Super Moderator Join Date: Feb 2006 Posts: 2,379 Blog Entries: 4 Thanks: 118 Thanked 319 Times in 238 Posts Rep Power: 60	Hi Priyanka, 1.What are the disadvantages of overtesting? Overtesting an applicationmean,trying to test each and every possible combination of functional flowswhich is never possible in this ideal world. Most of the customers may not use all the features of the application(especailly if it is product rather being project)and thus wewill wasting our resources unnecessarily on those low priority aspects of the product. Rather spending time onthese low priority features, if we concentrate on high priority/most frequently used features, that may yeild high productivity. Again, a point to stress here is, it is never possible to release a bug free application. But, by testing we can only minimize the cost of the bugs. 2.What happens to the test plan if the application has a functionality not mentioned in the requirements? It clearly represents the communication gap between PM(Project Management)/Dev team and QA teams. In case of such situations, first try to understand the new functionality that is added ( by contacting dev or PM POC's) and then know what is the business requirement for it and get ajustification from them.Then QA should be able to guess what will be its impact on the over all functionality. If it impacts the functionality or changes the complete functionality, then the QA should modify their scripts accordingly. If the new functionality does not have any impact on the functinality then there won't be any chages. But, in real time, the situation will be, we have to uplift our scripts covering the new features. If you have any more doubts or if I am not clear on any aspect, please let me know. Thanks, Krishna __________________ Looking for trainees for a start up company
Offline

08-12-08, 11:14 PM	#4 (permalink)
AjayKumar.Kataram Senior Member Join Date: Aug 2006 Location: Hyderabad,India Age: 30 Posts: 8,044 Thanks: 2,105 Thanked 425 Times in 303 Posts Rep Power: 124	Re: Dis Adv of over testing? Good one....
Offline

10-12-08, 05:19 PM	#5 (permalink)
aforarun Senior Member Join Date: Sep 2007 Location: Bangalore Age: 27 Posts: 171 Thanks: 33 Thanked 130 Times in 40 Posts Rep Power: 17	Re: Dis Adv of over testing? Thanks Kireeti... Good info.. __________________ Arunsankar Value has a Value-Only if its Value is Valued
Offline

10-12-08, 07:15 PM	#6 (permalink)
antojap20 Senior Member Join Date: Oct 2008 Location: chennai Age: 27 Posts: 295 Thanks: 5 Thanked 61 Times in 33 Posts Rep Power: 10	Re: Dis Adv of over testing? Good Info __________________ Antony Prabhu Sr.Test Engineer chennai. view my Blog http://antojaptester.blogspot.com/
Offline

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)

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