For issues with partners in outsourcing testing, it is always important to go back to basics periodically to check the direction of the issue, and also understand if you are addressing the right problem. During customer engagements, sometimes we get too carried away and miss the point. To avoid such pitfalls, we recently invited one of our customers to address the team on the issues they had faced in the area of testing, while working with partners like Mindtree.
Well, the thought was risky and was like opening up a Pandora’s Box. But, when did testing shy away from taking risks? It was a good decision to bravely ask the customer to share their thoughts to the entire team. With her permission, I am now sharing the learning with you all.
Here are the top three issues as articulated by the customer:
Let’s take a closer look at each of them.
Testing is an expertise driven activity and there can be no substitute to a tester. A career developer is not the right tester. A testing professional is expected to think differently from a developer. The seed to this thought comes from a well-defined career path for testing. Organizations should give due attention to this career path. Most of the testing phases require attention from people who have dedicated their career to testing.
The second issue leads to lot of inefficiencies. In the IT Services industry, a testing professional is required to test different applications or systems involving varied end-user profiles. While exposure to different domains is desirable in the first four or five years of one’s career, beyond that period, the organization should support the need for a testing professional to focus on a particular testing type or an industry domain. Since Testing is the ultimate gate of quality before the exposure to the end-users, thinking about them is very crucial for an issue-free end-user experience.
Confidence, with the ability to call the spade a spade is a key virtue of a good tester. A testing professional without the self-confidence to expose a bug is a definite liability to the objective of independent testing. Service providers build this mindset of calling the customer as “God.” While this is absolutely right, it should also be taught that exposing a bug is not equal to offending the customer. A tester should be the “voice of quality”.
These were the key points that were derived out of the meeting. As always, it will be great to hear your views on this topic and educate the whole Testing community.