3 Things Transforming Testers into Rampaging Monsters of Fury!

TestFortExpert by TestFortExpert on 01/26/2015

3 Things Transforming Testers into Rampaging Monsters of Fury!

If you are a tester you have a very special mindset and as a result your inner world is a little bit different from everybody else’s. You are a calm person who loves everything and everybody, especially if those may be tested. Yet there are things that are transforming even the best of us into bloodthirsty irritated killers that are willing to destroy mankind out of mere fury burning like hell’s flames inside. Here are some of those things everybody who has been providing professional testing services has experienced.

  1. Release cycle acceleration. Continuous delivery does not mean constant delivery. I’ve checked the dictionary. Twice. Those words have different meaning. Software testers are having a hard time already by being considered as something slowing the process rather than adding value to it. Simply rushing QA will never give any positive results. It’s not that magic happens every time when an e-mail from a manager stating ‘hurry up’ is being received. If there is no time for tests management is simply doing something wrong within the entire organization and that particular something requires reconsideration.
  2. Awful code from developers. It’s as if they were typing it with one hand tied to their chair and a blindfold on their eyes. Testers should test areas of potential threats and hunt bugs rather than hunting features inside a large grasshopper. Unit tests and other measures from the development side would be nice and appropriate as well as static analysis and code reviews. That would save some time from testing.
  3. No access to required data. Surely there are understandable risks that are to be managed hence data is protected but when testers spend more time requesting such data from supervisors and administrators instead of actually running test then the process is going in the wrong direction at some point.

Surely those are not all things capable of frustrating any tester to the bone, but these are the most common issues that are generally spread. What is your personal red flag as a tester? How are you and your team overcoming them? Feel free to share in the comments below. We are open to any ideas and suggestions.

Image via Marvel Comics

We use cookies to ensure your best experience. By continuing to browse this site, you accept the use of cookies and "third-party" cookies. For more information or to refuse consent to some cookies, please see our Privacy Policy and Cookie Policy