Testers are like the tool in the hand of an engineer

By Alison Lillian Dixon

In case you didn’t know, an automotive engineer works behind the scenes to come up with new technologies and improve existing components inside a vehicle. They are not anything like your local mechanic, who does the annual “tune-up” on your car. Then you get software developers (developers) who, with assistance from testers, use software diagnosis tools to monitor, steer, observe and optimize existing software that has already been developed. This is no small job.

Testers growing in their field

A tester needs to be able to diagnose and facilitate conversations between the developer and the project lead or Management. They serve as the early risk detection tool, similar to a fire alarm, that warns you that there is a fire in your building and notifies the relevant authorities to take action. It is not for the tester to decide if the error should be fixed and by whom — that is up to the project team to decide and then schedule into the current or future development cycle and position it as future features or enhancements for the client. However, if the risks are not raised and addressed, it could negatively affect the down-the-line performance of the product.

When the team communicates and collaborates

Clear and concise communication is key to a better understanding of the requirements of the client and in delivering a product timeously. The common goal is to have a product free of errors. With the help of testers; developers can refactor their code without changing current functionality. But this means working together as a team and by being clear about what needs to be done; by when.

Having a software tester will not make your product “bug-free”

With all the diagnostic tools and processes, there is still the chance of a software defect or “bug” slipping through the cracks. The best way to minimize its impact and severity is to run rigorous testing. This sort of testing includes the kind that follows strict entry and exit criteria and covers all possible combinations of test cases and test data so that every possible bug could be found and removed before the product goes live.

Humans still can make mistakes

The primary cause of software defects is human error, which is why it is so important that we learn to understand them. Software defects are, by nature, manifestations of a cognitive error made by developers. In the early 1970s, the cognitive nature of software was identified, but more recently significant progress has been made on the human error theory that looks to prevent software defects. So until we can fully automate the testing process, we need to use the tools that we have available to us, as well as follow all the appropriate testing principles and procedures. Thus, assisting in the end goal of testing thoroughly and successfully to ultimately hand over quality products to clients.

Acknowledgments

Thanks and shout out to my sister, Joann Julius for a great job on this edited version of the article.