“Do our automated tests take into account the notion that different people might value different things, and that one of the tester's primary goals is to recognize different constituencies and the ways in which their values might be threatened? “
Many people in our community think that as testers our goal is:
- To find bugs
- To prove that the application "works" as per the specifications.
- Run a bunch of tests and report the results,
- Develop some automation to speed up the execution of tests
This is statement from Michael is an extension or probably logical conclusion of the famous statement that is often associated with testing “Be customer’s advocate” (or “think like customer”). Michael seems to suggest that it is not only customer whom we should consider, as testers we think about all stakeholders and explore what each of these stake holders value.
A stakeholder is a person is who is affected by the success or failure of a project or the Actions and inactions of a product or the effects of service – Cem Kaner
In one of the comments for the same post, I found another worth quoting statement from Ben Walther …
“There will always be inputs into your system that violate the assumptions made in building it. A computer generated test will not be able to violate such assumptions.”
Very true … that is why testing is so challenging and exciting