WWF – Testers Vs Developers

My friends in development kept asking me that they can’t find my post for developers. In fact they have started forming a group to bang me :-)

I was travelling to my native for a weekend in rock fort express. Just had a thought that I should post a blog about the bondage between testers and developers. In IT industry we can even conduct a debate show (Testers Vs Developers) like “Neeya Naana” in Vijay TV.

Here you go with the blog on the same ...

I was just analyzing where this gap arises. It’s due to the misconception that dwells between the testers and the developers. This can be easily avoided if we eradicate the rivalry attitude between the two.

For Testers:

• The existence of defects in the application is not only because of the developer’s code. There may be many other factors too.
• Testers should understand their job first. Testers are not here only to find defects but to help the developers by communicating the gap at the earliest to deliver a quality product.

For Developers:

• Testers are not testing the application to just find an error on your code. A tester is the last person to test the application and acknowledge that it is fit for use.
• Testers reduce the developer’s burden by taking the responsibility of testing which was earlier a developer’s task.
• Testers will always be claiming that there is no sufficient time for testing. It is better if the developers give a clear picture on the activities that are taking place during the developing phase. With that the testers can plan their activities simultaneously.

The issue can be resolved by cultivating the following habits.

• Being transparent
• Have a Unique aim to deliver a quality product.
• Good interactions and sharing suggestions in a friendly manner.

Ability to work as a team by eradicating the mindset that the developers and the testers are from different team.

T-Together
E-Everyone
A-Achieve
M- More Let’s work as a team and achieve more!!

Here lies the passion for making a positive difference.