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:

Comments

Post a Comment

Popular posts from this blog

Testers doing test automation - is that the most important thing for you to do right now?

I've been thinking quite a lot about tester's moving to do test automation.  Lately beause of these three things: 1.  European testing conference , a great testing conference I attended couple of weeks ago. It is very cool due to many things; the way the speakers get compensated, the focus on the conferring side of conferences making it very easy for people to discuss stuff, the way the talks are chosen, and because there are also a lot of developers joining. So anyway when I was talking with several of the attendees, it was a bit strange how it was easier for me to talk about the product development as a whole with the developers, where as with the testers it more naturally moved into talk of automation and tools. Also on the open space, I think the majority of the topics pitched was automation or tool related. And quite little on the process or on the customer facing side of product development.  2. In my company there are a lot of different products and...
3 comments
Read more

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

Six reasons why testers should do code reviews

I have had quite a lot of discussions about code reviews. Quite many also with testers, by which I have understood that many do not do those. I will not start arguing here on whether code reviews are good/important or not. But I will list a few things why I think testers would benefit of doing them. 1. Code is the only documentation that is up to date . If you really want to know how something really functions, you want to be able to see and read the code. 2. Knowing more about the thing done enables you to do better testing . You can spot things that you should definitely test, and things that you probably don't need to test that much. Like extra things added by coder, usage&modifications of existing functions, data types, etc. And to arguments thinking that one loses their "independence" as a tester by knowing too much, I would worry a lot less about that than about testing stuff that you have no idea on how it has been built. 3. Improve logging . I obse...
2 comments
Read more