About Srinivasan Desikan

Srinivasan is Author, Architect, Advisor and Adjunct Professor in Software Testing. Srinivasan is currently working as Master - System Technologist at HP and has worked as Director of Quality Assurance and testing at Talisma, Siebel and at Agile Software as worldwide head of QA. Srinivasan has held different technical and management positions at Novell Inc and Wipro and was part of large testing and product development teams. Srinivasan is the author of one of the best selling book "Software Testing - Priciples and practices". Srinivasan is currently serving as the convener of the Quality forum with Bangalore Chamber of Industries and Commerce (BCIC) and conducts international conferences and guest lectures.For more details please visit: http://srinivasandesikan.blogspot.com/
   
   

  This article was published by “Software Engineering – Australia” (SEA) during June 2003. The content of this article   was also presented in ASIASTAR-2003 at Melbourne. This article is based on the experience of the author in   building the testing teams from scratch and contains few tips that would be helpful to managers and engineers for   creating an effective test team.
  It is very important to address incorrect perceptions about testing. Testing doesn’t stop with the finding of defects.   In fact, that’s where the task begins.

  This article was published by CTO Forum Aug-2008 and talks about how virtualization can help the testing teams in   reducing the cost, time, effort and efficiency of data centers. This article also talks about various types of testing   and their suitability to virtualization. It also contains a case-study of localization testing and it’s applicability to   virtualization.
  System virtualisation is a valuable piece in an R&D test lab environment as it provides cost advantages in terms of   power, cooling, and real-estate space while it simplifies hardware managemnt.

  This excerpt is from the talk by Srinivasan Desikan in Step-IN panel discussion. This document tries to clear   several perceptions of testing using some of the most powerful slogans and punch-lines published by The   stickyminds.com. The recorded version of this speech was enjoyed by several organizations at Bangalore.
  I had been to several testing conferences over years, however the topics for panel discussions are almost the   same. But the way it has been presented changed a lot over years. 5 years back the topic was “Is testing an   engineering discipline?” 2 years back the topic was “testing – an engineering discipline!”

  With economic slowdown hitting the industry at the space of every 5 years, one thing that will help all companies   and individuals is “skill & competency”. This article which was published in PCQUEST Aug-2008 talks about few   points that would help in improving quality while improving productivity.
  What is it that bugs software developers and testers repeatedly? It is the changing requirements of customers till   the product finally gets delivered. The software testers and developers have to modify their product as per client   requirements and that too in a stipulated time.

  This article was published by Express Computer in 2003 part of NSST conference. The same article can also be   found in stickyminds.com. The content of this article was presented in PSQT/PSTT conference twice and was also   presented in STeP-IN conference twice. This article enjoys thousands of downloads by the practitioners.
  There are several definitions and perspectives exist in the industry. The purpose of this article is to bring the best   breed of those definitions and methodologies based on the personal experience of the author in software product   companies.

  This is an experience sharing article posted in stickyminds.com and is an output of the collective experience of   testing several server based products for scalability and performance. This article contains few points that may   help test engineers in performing non-functional testing.
  This article is intended to discuss the concepts of performance and scalability testing with respect to four resources   CPU, disk, memory and network. The four resources are related to each other and we need to completely   understand their relationship to implement the strategy for scalability and performance testing.