Agar hum nahi honge to tumhara kaam hi kya hai company me…..
Tumhe req to samajh nahi aati bas aise apna bug count badane k liye bugs daalte rahte ho……
Tumhe coding nahi aati…. Firr IT me kya kar rahe ho….
These dialogues can be heard in any of the IT company (obviously from devs only).
Often the tester is seen as the anti-developer, with the developer standing for creation and the tester the destroyer of the developers work. On many occasions you will see their two departments almost fighting battles as each tries to prove its worth and capability.
According to one of my colleague the developer and their skill set are valued above the tester. Within the project life-cycle, development is considered essential, testing as a “nice to have” but not mandatory. Initially I differ from her but unfortunately, sometimes I feel the perception of testing as a inferior role in some developers mind.
When code goes live and the volume of bugs is minimal with positive user experience, it is rarely the tester that is thanked for their diligence: more likely to be the developer thanked for their fantastic software. And on the other side if client has reported bugs in software then the whole blame goes to tester.
The developers mind set is one of creation whereas the tester is one of destruction. There is no doubt that the tester becomes redundant if there is no development whereas the opposite is not true. Many projects still run today with no focus on testing and the burden is placed on the users to experience the problems and report them.
I almost fought with one of my senior when I heard him saying “I would recommend that the "not-so-hot developers should be made full-time testers”. Many of the same skills and tactics that make a developer successful also make a tester successful. How can he be so sure that bad developer will be a good tester? If you value quality a lot, then you may should the specialized skills and tactics that a tester brings to the project, since that's what testers specialize in.
Imagine a scenario: Organization doesn't value testing because they have a low opinion of testers and think developers can do it better. Organization, have communication issues or personality issues, whatever.... Organization notices that they are decides to take a chance. It allocates some developers to be testers. Those developer-now-tester's struggle in their new role for all the same reasons they struggled with their old role (they don't read, are slow to learn or adapt not getting increased value from adding testers.) This lowers their opinion of testers even more. The call goes out for more developers to become testers to help stabilize the experiment. Now that the tester negative perception has been "confirmed", even worse candidates are sent over to become testers. If external candidates are hired, they are hired by developer-now-tester's who don't know what a good tester looks like - so they hire those like themselves. Those developer-now-tester's struggle even more in their role.. organization notices that they are getting no increased value from adding testers. This lowers their opinion of testers even more. The experiment is over. They gave it a shot, it didn't work out. Their earlier assumptions that just having developers is "confirmed." They knew it all along anyway, right?
Perhaps the above case appears to be dramatic to you but it is not far from true.
This “anyone can do” attitude is followed in many IT companies and QA job is treated like plug n play(i.e.. anyone can perform)
Subscribe to:
Post Comments (Atom)
Nice topic :) the way u have explained the scenario is really nice. rest is mediocre I mean the thoughts are not looking original (myt be inspired from some one ;))
ReplyDeleteReally , It is very good topic to raise
ReplyDeleteI have seen similar kind of comments from dev side
"Hum agar code nahi karnge to tum kya karoge"
We need to do something else to change this perception
Hey Kamlesh.. nice thoughts.
ReplyDeleteBut I must say that this is not the case everywhere.
Most of the times Dev's are just scared of QA's. Scared that what new bug this person going to file.
Also 'Tumhe req to samajh nahi aati bas aise apna bug count badane k liye bugs daalte rahte ho……' I think this will happen only if the tester is really dumb.
Developer-now-tester's is really not happening. Although tester might not be able to do what dev's do (that is write code), but the vice versa is also true.
Devs never have enuf patience or the creativity that a QA has, which is required for breaking the code. They are engrossed in making the code work, which is quite essential actually, but it leads them into ignoring the small but vital points which the end user will not be comfortable with.
QA just show them the path of making the code complete.
Of course a dev if wanted can become a QA over a period oftime. But again same is also applicable if QA wants to become a dev.
One more thing, QA's are not meant to destruct the code. Thought its called breaking the code, its not the QA whose breaking it. The code is already broken. QA just identifies that its broken.
And last, QA - are they required anymore???
If the devs were so sensible as to 'identify' and 'accept' the mistakes in there own code, I guess QA's might not be required.
But alas, devs aren't that intelligent. Else why would there be so many testers in the world! Not to mention they are paid equally like devs. :)
QA ki dil ki aag bahar aa gayi bhai kisne kya bol diya esa?
ReplyDeletewhere's the like button?!...you wont believe that i have an interview today n i was thinking the same "paragraph 4" to quote in interview in a constructive manner...anyways,lot more to say but this isn't the right time for me...wud get back sooon...and lemme tell u...here while MS i have realized that coding is equally essential for a QA as a dev!!!....so i'd suggest that u shud start coding to an extent by urself ;)...catch ya soon....bbiii...nicely said :)
ReplyDeleteBunty.... All fine in ur company??
ReplyDeleteDid u messd up with your colleagues??
Itni bhadaas devs k liye.
I partially agreee with u.QA condition is not so pathetic as u have mentioned...
really liked your post... worth a read by EVERY person in SW industry... yeah, it's frustrating when testers keep filing bugs, but i think they are EQUALLY important as a part of the project... a project can't be successful without QAs :)
ReplyDeleteInduuuu....very well said(last line)
ReplyDeleteand above it, gud to see that finally our opinions matched (nahi to tu hamesha mere opposite hi rahti thi :p
Hey Kamlesh
ReplyDeleteyou written my experience here. specially these lines "rarely thanked to the tester..."
@ archana ...most of Qa's has experienced this...
ReplyDeletegood one...
ReplyDelete