When I search online for software testing services, I get a bunch of results showing companies that provide software testing as a service and rightly so. However, I have a slightly different take on this, coming in with a perspective that software testing should be viewed as a service not just in the context of such service providers but also within product companies. Independent testing that was held high in the last decade is gradually losing its positioning in the current times, not because of the downhill trend in software testing, but primarily because of the increasing need for collaboration between software testers and the rest of the product disciplines. In such scenarios, one fear the software testing industry faces is whether independent testing is dying – are we diluting the focus of this discipline – should we resurrect it? While this is an individual call each organization should take depending on how mature the quality effort is at their end, one broader solution that would help is to view software testing as a service whether you are a product or a services company. And when that mind-set is inculcated a lot of benefits accrue – whether this be in a service like delivery model which is measurable and objective, a collaborative yet consciously distinctive quality effort, a disciplined approach to quality, a respected career for software testers etc. In the current challenging times for this profession such a services like implementation model will certainly help bring in a rejuvenated focus.
And as I wrap up this short post, I am happy to quote a recent example where we have been talking to another services provider (in some sense a competitor of ours) about testing a product they are developing. It is very exciting to see the importance they have been giving to independent yet collaborative quality for the product they have been working on. That is the services mind-set we should ultimately get to irrespective of whether the testing group is internal or an external vendor that is engaged.