Home > Method > QA – Offshoring, OnDemand what’s next?

QA – Offshoring, OnDemand what’s next?

When I need to learn how certain system works I start by investing some time at the lab with the QA team.

The best software knowledge and expertise lies in the mind of the testers. They end up being the best resources helping developers, tech support, services and other testers (and me). They spend so much time with the system, first trying to make it work, then using what that works to test other functional areas and then breaking it again till they become so intimate with the system that even the ones who built it looses in argument about how it really work (vs. how it should work).

As a development manager I include testers in any discussion from requirements anlaysis and throughout the entire project life cycle. Their input is invaluable and is helping to protect developers from getting in trouble. Btw, I don’t appreciate introverted testers.

The purpose for this preface is to  show my concern about how the business treats this function. Testing is expensive and even big investment in automation that is crucial for scaling development (across OS, web/app severs, locale and databases) does not eliminate the need for the human touch and feedback.

So far the corporate came with solutions such as off-shoring; exporting this effort to places where labor is cheaper or contracting to cap expenses. Now I learned of a new way to deal with the QA cost: uTest– On Demand (SaaS)testing service. This time exporting the system of record. uTest also plan to offer a new pay-per-bug service where two type of test engineers could contribute to the quality of a system and earn money: expert and others.

From my experience working with large enterprise software organization I learned that some protect themselves from new buggy versions of the product by running their own QA team building and executing full regression test suites that even include automation. I wonder if they end up trusting a (SMB) vendor that use this kind of service.

I like to have both people and methods close but we’ll have to wait and see which method prevail.

Categories: Method
  1. January 12, 2009 at 1:24 pm

    The thing about uTest is that we don’t really replace traditional testing, but instead we supplement it. There’s always a place for good TDD led by experienced testers who are directly involved in the design process.

    The uTest on-demand model, on the other hand, makes it easier for smaller companies to get good testing earlier (before they hire experienced testing leads) or for larger companies to get more testing whenever they need it (in addition to their experienced testing leads).

    uTest Marketing Manager

  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: