Tester’s Rules of Fruitful Communication

Tester’s Rules of Fruitful Communication
July 28 05:43 2016 Print This Article

An experienced specialist of software testing or mobile testing knows that having strong communication skills is a great prerequisite for professional’s overall success in a software testing company.

There are plenty of training courses and seminars dedicated to the conversation skills development techniques. Let’s review those of them that can improve the tester’s ability to effectively participate in IT processes.

How Can Testers Improve Their Communication Skills?

  • When describing an issue, testers should specify exactly which feature does not work. If multiple functionalities are broken, they should briefly explain it without excessive generalization and avoid remarks like “Regression testing shows that nothing works.”
  • It is better to use exact names of elements, for example, “select the File menu item.” This will prevent ambiguity and confusion.
  • When proving that something does not work, testers should explain what concrete actions they have taken. For example, if a bug is found during automated testing, a tester should investigate and list the features affected by a bug, specify which tests were failed and provide other essential information to developers.
  • It happens that, for example, project manager and developer discuss an issue, agree that it is not a bug, but forget to share it with others. That is why it is helpful for a tester to primarily discuss a potential bug with a team, just in case.
  • Testers should ask questions if something is unclear for them. If a tester has a lot of questions, it is better not to ask them all during the general meeting but save them for private discussions with project managers.

If a tester sticks to these recommendations and behaves accordingly, his/her communication with colleagues will be highly effective.

Related Posts:

About Article Author

view more articles
Nataliia Vasylyna

View More Articles