Skip to main content

Tester's service promises


My company has a monthly news letter, each month having a different theme.

The theme of the news letter is "Service promises" where we discuss and think what is and what should be the service promise we give to our customers. This got me thinking, what is my service promise as a tester, and then spent an hour creating them. Here's the list


Tester's service promises


●     I promise to test
●     I promise to tell if something threatens my ability to test, including my own lack of knowledge
●     I promise to try to find out my testing purpose, i.e. why I am testing
●     I promise to try to decide what and how I test to fit the purpose of my testing
●     I promise to report everything that to me look like things that could threaten the value of the system (to someone that matters)
●     I promise not to find all the bugs in the system I am testing, nor to give out information that would for someone look like I have
●     I promise not to test everything in the system, nor to give out information that would for someone look like I have
●     I promise to do my best to understand the context, the business and the risks associated with them, in order to do better testing
●     I promise not to become a gatekeeper or a sentinel of quality. My job is to provide information in order to assess and analyze the quality, not to demand a certain level of it.
●     I promise not to label myself as a quality assurer. My job is to provide information in order to assess and analyze the quality, so that other people can assure it.
●     I promise to make mistakes, admit the mistakes, and learn from them.
●     If given trust, I promise to make more mistakes.
●     I promise to not to try to look good in the expense of other people, including but not limited to analysts, coders, other testers, end users, and project managers
●     I promise not to keep all these promises. But I promise to try.
●     I promise not to do things just because I am told to do so.
●     I promise to try to fight the apathy, cynicism, and fear that sometimes tries to take control of my work. As fear leads to anger, anger leads to hate, and hate leads to suffering.
 

O yea. I also promise to rethink, remove, and add some of these promises.

Labels

Labels:

Comments

Post a Comment

Popular posts from this blog

Testing drunk

(My first blog writing ever.) I've been thinking a long time that it's funny how many bugs I find by accident. Try to do something, make a mistake and boom - a bug is found.  Making the mistakes intentionally doesn't quite work - that's why they are called accidents I guess.. So I've thought of ways to make myself more prone to accidents, coming up with an apparent one; testing drunk. TUI (testing under the influence). So this I gotta try. More to come on that later.
3 comments
Read more

Periodical retrospectives are lame

  "You got nothing, not a single thing?! Well lets just end this here then." I remember well when I said this, being very frustrated. About ten years ago I had been working as a Scrum master for a team some months, and putting quite a lot of effort into planning our scrum teams sprint retrospectives. Lot of work also because I felt we were not getting too much out from them; not very good discussions, very few actions, and even the few actions we did come up with did not stick.  And then it happened: a retro where none of the participants came up with anything to say about the sprint. Regardless of the retro topic boxes, reading of books on retrospectives, getting inspiration from tools like retromat.org, having them in different places, using all kinds of different formats and rainbow coloured post-it notes. Not a single thing. Blank.  So then I said the words, out of frustration, mainly to myself. Why couldn't I get this thing everyone is so hyped about to work? Af...
Post a Comment
Read more

The miseducation of Exploratory Testing

I've been noticing a phenomenon lately, that is the over/misuse of the term Exploratory testing. As many testers seems to have kind of settled for the Exploratory testing paradigm and have moved to new frontiers like checking vs testing , it seems many other parties are really getting into it, and of course understanding it in different ways. Couple of examples of this phenomena: 1. In my final days as a consultant one of our sales people, had visited a customer who had no experiences about testing, but specifically requested the sales man to give a offer on Exploratory testing 2. I just looked at the program of Agile testing days 2013 , and really many of the testing related talks were labeled about Exploratory testing, although to me many seemed to talk/practice testing in generally It's nice that the Exploratory testing is gaining momentum, but I am also a bit worried about it. The examples listed above could be supported by many others, which kind of give me the impr...
2 comments
Read more