Quotes About Testers

I control the conditions so my testers become my testees.

How can we hope to catch all the configuration options in an entire system? At some level we can't, and this is at the heart of what professional testers do.

The best testers were masters at deducing the chain of events leading to a failure. They provided code writers with a virtual road map to fix their bug. The worst testers offered little more than a description of the hangup and a half-baked hypothesis of the cause. Manheim

The best testers were masters at deducing the chain of events leading to a failure. They provided code writers with a virtual road map to fix their bug.

Customers may have a good idea of the general behavior they want to see, but testers are good at looking at "happy paths" and asking what should happen if something goes wrong. "Okay, but what if login fails three times? What should happen then?" In this role testers amplify communication.

You may be trying to drive in a particular direction that people don't necessarily understand at first. In our case, we knew the users we had in mind for this product. So in the early days, we looked at our customers, really just testers at that point, and we paid extra attention to the teams we knew should be using Slack successfully.

Most testers I've known are perverse enough that if you tell them the "happy path" through the application, that's the last thing they'll do. It should be the same with load testing.

Most software is designed for the development lab or the testers in the Quality Assurance (QA) department.