Misconception:
Software testing is about finding many ways to break the software
Conterargument:
Bugs and errors may be found whilst the tester operates the software and it is important to record any found. Testers do not aim to or purposely try to break the software (its not pen tesing); Instead they note down any errors found and request improvements with the intention to enhance the functionality and to see if requirements are met. It’s more of a positive approach rather than causing damage or destruction in the testing process.
Counter-Argument:
Testers can’t test everything.
Testers have to keep to a strict deadline for when a software has to be released, so in order to keep to it they have to decide what scenarios are most likely to happen and test those scenarios. Also, testing for long amounts of time can become very tiring and physically challenging. Testers have no idea what a customer would want when using the software, so they try to make sure the core functionality of the server is working.
A common misconception which I have come across is that testing is a single task which takes place before the initial release of the software.
This is a big misconception, and testing is actually consistent throughout the whole of the software development lifecycle. This ensures that testing does not only just see if the software works as expected, but uncovers information which would otherwise be ignored in the development of a product.
Misconception: Anyone can test software. Counterargument: Testing isn’t just about writing tests and performing them. Testers need to be creative and curious. They also need to be effective communicators. The amalgamation of all these traits is necessary to properly test software.
Misconception: Testing is clicking at random places.
It is a common myth that testing is just clicking on UI randomly and tracking details in excel or other documents.
The reality is that testers perform very well-defined test steps to assure that the UI/APP is working in exceptional cases as well.
Since a user does not have boundaries on what they can and cannot do, the same goes for testers. This is why it is important to explore the UI, which might look like lots of random clicks. It’s a very vast area which needs lots of skills .
‘‘Software testing is too expensive’’- Without continual testing of a product, the risk to the business is extremely high, with the possible costs massively outweighing the benefits and funds to run testing of the software. For example, this has occurred with various banking apps recently, whereby the maintenance of the apps has not continued their testing journey, allowing for bugs and security breeches to affect the quality and expectations of the product.
Testing is not necessary or as important as development.
The first step in a proper software development lifecycle is requirements gathering. As a tester, one of our primary goals is to interface between customers and developers in order to clarify those requirements. Part of our quality assurance is ensuring that those requirements are clear and met. Without the testing role, we could not be sure we have built the right thing for the right reasons. Even if something was developed, if we missed the goal, then the software development project risks failure. Testing is essential.