Myths About Testing

Picture1

Myths About Testing

From the beginning of my career, I’ve been hearing about many myths about testing and testers. In this blog, I thought of sharing with you a few of them and why they are ‘myths’:

Anyone can do Testing without any experience and knowledge:

Anyone can test the UI by playing with it, but what sets QA apart is the ability to see the application from the user's perspective and determine its suitability for customers. This is what makes testers special.
Based on their experience, testers can bring forth numerous scenarios and suggestions for the application, which can only come from their experience.

Manual Testing Has no Scope

I strongly disagree. For example, if a button is functioning properly, only then can you write test scripts to automate its testing. Therefore, someone needs to test the button manually first.
You cannot automate an application unless it has been manually tested by someone.

standard-quality-control-concept-m-scaled

Testers do not update their skills:

Initially, there was only functional testing, but now there are additional types such as API Testing, Performance Testing, and Security Testing.
Nowadays, there are automation tools available for each type, making learning a continuous process.
Each company utilizes different Defect Management and Test Tracking Tools, so testers must continuously acquire knowledge in these areas to keep themselves updated.

Application will not be released if there is an open bug:

However, it is not true that a tester can simply give sign-off by labeling open bugs as 'Known Issues' in the Release Notes. While there may be some bugs that do not have an immediate impact on the application, it is still essential to address and resolve them before providing a sign-off.

Developers can do the testing themselves and no Separate Testing Team is required:

Many people think that way, but with that approach, one of my previous companies ended up with a huge list of bugs reported by clients.
Testers have a different perspective when looking at an application compared to the person who developed it.
It is always better to involve testers in testing the application, otherwise, it can result in a loss of customer trust due to bugs and poor quality.

Testers do not have future:

I have been hearing since the beginning of my career that testers will not have a future after 3 to 4 years. However, I have completed 11 years and still have much more to come in my testing career.
The innovation of new products and the need to update existing ones according to current trends will never end, and testing will continue to flourish

Want to learn more?

Scroll to Top