Beware of the broken promises as a tester

Sajitha Pathirana
5 min readApr 25, 2024

Project Manager: Hey Testers, have you completed testing everything? Did you cover all the scenarios?

Testers: Yes, we covered all the scenarios, completely tested the application and reported all bugs.

Sounds familiar? And have you ever got embarrassed with your word? Then, this article would definitely reflect the situations you have faced in your career as a tester; miscommunications and misunderstandings you have had along the way. Further, let’s discuss how to be cautious when we say completed.

Beware of the broken promises as a tester

Completed testing offers lots of ambiguity. Often it is more than stated or in other words, the expectations would be higher than what was meant. Hence ‘completed’ is something that should be used with ultra care. Let’s check some of the phrases that offers the ambiguity and misunderstanding.

Completed the discovery of every bug in the product.

As the testing principles states, testing shows presence of defects and does not guarantee the absence of defects. The main idea of testing is to identify problems and fix them beforehand deploying to the production. However, there may be bugs that were not uncovered during testing.

Isn’t it a problem?

--

--

Sajitha Pathirana

A Test automation enthusiast, passionate to help the teams to enhance their testing journey with his decade of experience in the field.