Imagine an Explorer who lost his way in woods. Now, he’s got one option i.e. to track his route, make markings to avoid visiting the same area again and again. He has to keep notes of the time, sunlight direction, markings on the woods, areas covered etc etc. Similarly, A tourist in a new city always makes notes of the places to visit or visited. Imagine how important it is for a Tester to make notes while doing Exploratory Testing (an unplanned activity) or writing notes of something suspicious you come across while testing, to foster better communication and remember important things which are otherwise ignored if not written down.
Remember when we were in School / College we always used to take down notes of lectures and re-read them to understand the topic further in detail.
A Tester writes notes, pointers, bugs, important messages, journals to communicate information, reports, views, observations. They need to make sure no important information is missed. To communicate effectively, penning down your thoughts, activities is very essential. But a poorly written information may not help you as a tester, the project or the team. Testers can always learn the art of writing once they understand the importance of it.
Testers who submits incomplete, hard_to_understand information fails in their presentation. Details provided are lost in translation when Tester:
– makes use of very long sentences thus derailing the issue under discussion
– writes incomplete sentences to only create confusion in reader’s mind
– do not focus on the vocabulary
– too many issues presented in same bug report
– gives partial information and assume developers and team to fill in the blanks