Phy-gital Roundtable: Breakfast Roundup from Germany and Netherlands

02 May '15 | Debjyoti Paul

German Shoppers: Meet Them in the Fast Lane to Phy-gital

15 January '15 | Ralf Reich

Shoppers Will Share Personal Information (But They Don’t Want to be “Friends”)

15 January '15 | Anil Venkat

Modernize or Perish: Property and Casualty Insurers and IT Solutions

14 January '15 | Manesh Rajendran

Benelux Reaches the Phy-gital Tipping Point: Omnichannel Readiness is Crucial

13 January '15 | Anil Gandharve

The New Omnichannel Dynamic: Finding Core Principles Across Industries

13 January '15 | Debjyoti Paul

Technology does not disrupt business – CIO day 2014 Roundup

02 December '14 | Anshuman Singh

Apple Pay – The Best Is Yet To Come

02 December '14 | Indy Sawhney

Digital transformation is a business transformation enabled by technology

01 December '14 | Amit Varma

3 Stages of FATCA Testing and Quality Assurance

06 October '14 | Raman Suprajarama

3 Reasons why Apple Pay could dominate the payments space

18 September '14 | Gaurav Johri

Beacon of Hope: Serving Growth and Customer Satisfaction

05 August '14 | Debjyoti Paul

The Dos and Don’ts of Emerging Technologies Like iBeacon

30 July '14 | Debjyoti Paul

What You Sold Us On – eCommerce Award Finalist Selections

17 July '14 | Anshuman Singh

3 Steps to Getting Started with Microsoft Azure Cloud Services

04 June '14 | Koushik Ramani

8 Steps to Building a Successful Self Service Portal

03 June '14 | Giridhar LV

Innovation outsourced – a myth or a mirage or a truth staring at us?

13 January '14 | Ramesh Hosahalli

What does a mobile user want?

03 January '14 | Gopikrishna Aravindan

Testing Times

Posted on: 01 October '09

Welcome to this testing blog. Taking inspiration from my colleague, John Scarborough, I have signed up to contribute to this blog dedicated to all facets of software and hardware testing. We will discuss about the evolution, trends, challenges, myths, best practices pertaining to the testing domain.

Testing, in last few years, has grown in its importance and assumed a critical role in directly influencing the quality of products and applications. Many organizations both product and enterprises be it large or small are investing heavily in setting up dedicated testing teams. Companies around the world have seen the value that testing can deliver with respect to improving customer satisfaction, saving costs, mitigating risks, and increasing time to market.

In my daily scheme of activities, I interact with many customers, prospects, industry analysts, thought leaders, and co bloggers in the testing domain. Needless to say, we have very interesting discussions around testing and I look forward to share my experiences and opinions on some of the testing aspects in my subsequent blogs.

In my next few blogs we will talk about some business and technical aspects of performance testing. Let us take a fundamental look at how companies perceive performance testing – their myths about performance testing and challenges that companies face in testing their products and applications. Then we can move into the very interesting topic of automation tools and performance measurement.

Do let me know your thoughts and experiences that you might had with performance testing.

Mindtree Blog Archives

Mindtree blog Archives are a collection of blogs by various authors who have independently contributed as thought leaders in the past. We may or may not be in a position to get the authors to respond to your comments.

  • Sanjay

    Hi Subodh,

    It’s nice to see your first blog entry.
    I think for performance testing, first thing is to determine why its absolute must to do and once that decided next focus could be to identify when, what parameters to measure, cost required to setup the environment and tools with return objectives.
    It would be great if you share your experiences in cost/ benefit analysis on the investment for performance testing as in typical cases it’s pretty challenging to repro the issues seen in long haul testing and there is no guarantee that those issues will ever crop up in future so the time spent on it is ideally lost with no tangible outcome and this goes in cycles and finally product get shipped with zero performance fixes but tons of real hidden bugs.
    For example company ‘X’ spends 12k per month on a resource ‘R’ to do performance testing, how do you measure the throughput, will it be in terms of number of tests written/ done, bugs identified and how that impact the quality of overall product instead of spending that amount in writing new features which will have direct impact in the product over its competitors.

    There is lot of good basic stuff about performance testing @ in addition to this, I hope your real experience of more than 16 years in the field will enthrall the readers and they will be eagerly waiting to see your next … blog entries like me 🙂

    Best Wishes!