I am dedicating this post to all my
Tester and Developer friends. Reason behind writing this post is to analyze the
sweet (not really ;) relation between tester and Developer and finding out some
solution to make it better J.
It is very common everywhere
developer thinks that tester’s are trouble makers and there is some bitterness
at some point between these two roles.
So; when we got lots of bugs
to fix and count increase, developers get frustrated at the number of bugs and
some time on the person as well and this is where the debate occurs about the
valid bugs, invalid bugs. A Developer always tries to prove the bug is invalid
or it is a feature; some of the common replies which we get in this situation
are:
“That’s weird…”
"It works on my machine"
"No user would ever do that"
"That's not a bug, it's a feature"
"It's supposed to do that."
"No user would ever do that"
"That's not a bug, it's a feature"
"It's supposed to do that."
There is a long list available about
the developers reply to testers but t I have just written which I have heard
frequently.
Now the question
arise that; is it all about the Developers?
Hmmm…..Answer for this is
simply No. In this game these two players has different and opposite role and
to make this relation better both need to work together as team.
A Developer needs to
understand that when we raise bug then we are not criticizing a developer or
not pointing the mistake in the person and on the other side a Tester
should give the proper information about the bug you got and about the scenario
in which it has occur and what impact it is going to have in business.
Developers and Testers can actually help each other in many ways; for example a Devloper can help in the following ways:
- By
sharing information;Since you have developed the product so you can share the information about the diffrent paths and the impact and vital informaiton which you think could help to make the product better.
- Before
you give any of the above given reply; please give it a thought that
tester is not pointing out mistake in you; It’s just that he/she has
raised the bug before client will raise; So spend some time in understanding
the issue rather than just simply rejecting it.
There are many ways in which a
tester can play a big role to make this relation better; tester's can help in the following ways:
- Do not hide your scenarios thinking that towards the
end of phase you will raise it as a
bug; If you have got something in your mind share it with the team and
this way we will not only build a
good relation but also will have a better product because when both the
parties shares the information they both
can help each other in understanding features
which they might have missed.
- Talk frequently with the developers; don’t just talk
with them when you have got some issue.
- Raise a bug in a way so that it should not hurt the
feelings means raise the issue in a positive way.
- Before raising the issue do some research yourself; for
example: if you are trying to open
some folder in some directory and you are not able to open that then just
blindly don’t drop the email; At least first check if you are in the
proper directly if the path is proper or not.
There are many more things for developers and testers which i can write about but I am just keeping it short :).
So now all
my developer friends please share your experience and write what kind of help
you think a tester should provide and vice versa my tester friends what you
think the developer should do or should not.
You can also share any quote which you might have heard from a Developer or from a Tester!!!!!!
