Hello, fellow testers, Thamsil Ahmed here. In this blog, I would like to talk about some important dos and don’ts while testing.

Testing the software is a very crucial phase in the Software Development Life Cycle (SDLC), as it determines the level of effectiveness and quality of the end product and helps to get perspective when it gets into the hands of the intended users. Therefore, the testing phase is performed with utmost attention and care. In this article, I have compiled a few dos and don’ts when performing a test. Let’s start with the must-dos.

Dos

• The person performing the test should be capable enough or must have enough knowledge according to the scope of the test.
• It is very important to go through the necessary documentation provided to understand the product under test and the areas to be covered.
• Make sure that all the prerequisites are performed before starting to test any particular section, as not doing so will hinder the testing process.
• Plan in advance and make sure to allot a specific timeframe for testing to avoid any kind of distractions.
• It is very important to understand the severity of the bugs being reported, to give the most preference to the critical ones, followed by the others.
• Always focus on one section of the product at a time, instead of jumping back and forth.
• Always make sure that the bug you are reporting is free from grammatical errors.
• Always make sure to provide all the evidence as required.

Don’ts

• Assumptions should be completely avoided. Report a bug or update the test case only after seeing the error or the bug when performing a set of actions.
• Do not report bugs that have been already reported. Always use the search option in the bug tracker to make sure that the bug isn’t reported.
• Do not have a mindset where the focus is completely on finding a bug no matter what. This may lead to the tester performing steps or scenarios that the end users are less likely to perform.
• Never neglect any defects in the products, no matter how small it is. As long as it is within the scope mentioned, it should be reported.
• Never perform the test in haste, as this may lead to missing out on many bugs or defects in the product.
• Do not test in environments other than what is being asked. For example, if asked to test in a specific model of a smartphone, make sure that particular smartphone is being used for testing.
• When reporting a bug, make sure the keep the description short and sweet, as it is better for you and the person going through the bug report.

I hope you all will keep the above things in mind before starting to test. Thank you for reading and happy testing!

This article is the sole responsibility of the author. By submitting their work to our blog, authors affirm that the content is original and does not violate any copyrights or intellectual property rights of third parties.