Testers aren’t mind readers. We’re not psychic or telepathic, either. Please write your test cases and review our bug reports accordingly.
Your QA Testers
Many testers dislike seeing the dreaded “Working as Designed” rejection reason on our bug reports because, in many cases, we had no idea it was designed to work that way. To us, it just seemed like something wasn’t quite right, and it’s our job to tell you these things.
In fact, if a tester who has the perspective of a new user (someone who has no prior experience with what they’re testing and sees the environment in a way a brand-new user would) writes up a bug report on a feature that seems to be broken or working poorly, there’s a good chance new users will also think the same thing. Perhaps you should review the design and user experience to see if there’s a flaw there.
After all, quality assurance is not just about telling developers when a page errors or when a link is broken. It’s also about telling you when your software does not work in such a way that a user will find it to be a useful, quality, worthwhile experience.
It might seem like a pain in the butt, but we’re really just trying to do our jobs and help make your project a complete success. Really! We’re on the same team, I promise.
When you ask us to test something for you, try and do the following things. They will help us help you and, in turn, your projects: