Software testing is a crucial activity in software development and it determines to completeness of a product. Being a crucial activity it needs to be carried out smoothly without any difficulties. But in reality it is difficult to carry out testing smoothly. There exists number of factors and issues that alter the smooth happening of testing. Those factors and issues are collectively called as bottlenecks. This work aims at the process of identifying the bottlenecks that are very common to testing, bottlenecks that are application specific and testing type specific, analyse the reasons and provide recommendations that will make Software Testing[1] to happen without bottlenecks or with minimum bottlenecks. This work was carried out in two phases. Phase 1, was conducted to know and understand the existence of bottlenecks in software testing. Phase 2, deals with the analysis of bottlenecks and recommendations to avoid or minimize bottlenecks.

IST, UAT, SUT, SRS

[1] Brain Marick, Classic Testing Mistakes, RSTAR97 conference.
[2] Amit Paradkar, Automated Generation of Self-Checking Function Tests, ISSRE, July 2002.
[3] Clay Williams, Thresa Kratschmer, A Technique for Generating Optimized System Test Suites, FSE 10th Symposium, November 2002.
[4] B.Hailpern and P.Santhanam, Software Debugging, testing and verification IBM Systems Journal, Vol. 41, No. 1, February 2002.
[5] Hongxia Jin and P.Santhanam, An approach to higher reliability using software components, ISSRE, November 2001.
[6] Clay Williams and Amit Paradkar, Efficient Regression Testing of Multi-Panel Systems, ISSRE, November 1999.
[7] Jeff Dunmall and Keith Clarke, Real-World Load Testing Tips to Avoid Bottlenecks when Your Web Apps Goes Live, MSDN , January 2003.
[8] Jeff Straathorf, Load Testing Intranet Applications Finding Hidden Bottlenecks, www.pureatria.com.
[9] Nina Godbole, Try Not to Make these Classic Mistakes, Information Technology October 2000.
[10] Mark Johnson,How to do good testing � an interview, STQE Magazine.
[11 Doug Nickerson, Software Quality Assurance � not for Dummies, www.computerbits.com/archive/2000
[12]BS 7925-1-1998, Software Testing Vocabulary
[13]IEEE 610, Standard Computer Dictionary.
[14]IEEE Std 1028-1997, Standard for software reviews.
[15]www.stickyminds.com
[16]www.rational.com
[17]www.mercury-interactive.com
[18]www.vlib.org
[19]www.thinkquest.org
[20]www.reality-test.com
[21]www.riceconsulting.com
[22]www.aptest.com
[23]www.worksoft.com
[24]www.computer.org
[25]www.sqatester.com
[26]www.stqemagazine.com
[27]www.softwareqatest.com
[28]www.rspa.com
[29]www.qalinks.com
[30]www.ibm.com
[31]www.sdmagazine.com
[32www.cmu.edu
[33]www.tamingthebeast.com
[34]www.testing.com
[35]www.unicomm.co.uk
[36]www.testingreflections.com
[37]www.perftestplus.com
[38]http://www.sisqa.com/SISQA_downloads.htm
[39]http://weblogs.asp.net/rosherove/articles
[40]http://www.theserverside.com/articles
[41]Roger S.Pressman, Software Engineering a Practitioner�s Approach, TMH
[42]W.E.Howden, A functional Approach to Program Testing and Analysis, IEEE Trans, Vol. SE- 12, No.10, October 1986
[43]Mordechai Ben-menachem / Garry s.Marliss, Software Quality Producting Practical, Consistent Software, Thomson Learning