Coffee With Narendra Babu – Testing Team Manager @ Google Bangalore
Its my proud priviledge to host Narendra Babu, Testing Team Manager @ Google Bangalore for a show in Coffee with Sundar. In this special episode, Narendra Babu clarifies some myths about what Software “Testing” Profile is all about.
Narendra completed his B Tech Computer Science from PESIT College in Bangalore. He then worked with Microsoft Hyderabad as a test engineer for 3 – 4 years. Narendra subsequently joined Google as a test engineer and has grown into a position to Manage testing teams.
Its over to Narendra Babu
Coffee With Narendra Babu
Brief Description of testing profile:
Test Engineering is a broad area and different companies/products approach Test Engineering in a different ways. To enumerate the approaches I am aware of
Model 1) Some teams decide to have very good unittests (written by developers) and engage test teams only in end to end testing.
Model 2) Some teams involve test teams in the complete software development cycle, right from the design to end to end testing.
Model 3) Some teams take a middle path where testing teams have some insight into the design/code.
The testing team act as consultants to manual testers and developers and ensure that the product is tested properly
Test engineering titles typically fall into two types
1) Software Engineer in Test/Software Design Engineer in Test
2) QA Engineer
The understanding in most cases is that category (1) test engineers are more into test automation and white box testing. Category (2) test engineers are more into manual testing.
As a test engineer you need to understand what model your team follows. Model 2 is preferred from a technical learning point of view. Model 1 is the traditional approach to testing in most organizations. Model 3 needs you to be pretty agile and proactive to make testing successful.
Typical education qualification required:
S/w Engineer in Test – Typically needs a engineering degree in comp sc or electronics from a good college
QA Engineer – Engineering in any branch or MCA (or equivalent) with good communication skills
Profiles with which this is confused with:
Normally the confusion is b/w SET and QA Engineer. Usually it is not clear as to how much of engineering work a test engineer does versus manual testing. That is the key to understanding a good test engineering profile.
Skills required to do well in this profile:
A good SET should be very good in communication and should have leadership qualities. Leadership qualities are needed to persuade the development team to adopt good testing practices, which strangely is difficult 🙂
Also one should think destructively. I have seen a few engineers excel very well as test engineers because their instinct is to find faults. Some others are not so good because they like to see things working. Not a good trait for test engineers 🙂
How to break software – http://www.amazon.com/How-Break-Software-Practical-Testing/dp/0201796198
Code complete – http://cc2e.com/
Thanks a lot Narendra!
For previous episodes of Coffee With Experts, click here.