My assignment at this moment is to define some test goals and goals from the test community for my client. This is an interesting job to do, because you have to go back to the start and define why we’re doing our work. During this task I had a nice discussion with a colleague and I will share this with you.

This discussion brought me to the conclusion that there are many things that have an impact at the perspective of software testing. An outcome for me is also, be very clear to each other (in this kind of discussions). If possible draw a picture or something to explain your thoughts.

The following picture is my conclusion and if you see this picture I hope it’s very simple.

But first let me tell you the discussion. I started with some definitions of testing and it doesn’t matter which one you take in general they have the same message.

Here are three of them:

TMap^®: Testing is a process that provides insight into, and advice on, quality and the related risks. (source)

ISTQB: The process consisting of all life cycle activities, both static and dynamic, concerned with planning, preparation and evaluation of software products and related work products 39 to determine that they satisfy specified requirements, to demonstrate that they are fit for purpose and to detect defects. (source)

ISO/IEC: Technical operation that consists of the determination of one or more characteristics of a given product, process or service according to a specified procedure [ISO/IEC Guide 2, 1991]. (source)

I chose the TMap^® definition, because in my opinion this was the best my client. After describing them I send an overview to my colleague. He send me this comment (free translation Dutch to Englisch). What he did is to split the definition into two parts and described, in my opinion, a combination of definitions and goals of software testing.

Goal of testing from the perspective of the test engineer: testing is doing research to give an answer to the question: Do we deliver the products with the correct quality to our customer?

Goal of testing from the customer perspective: Testing gives an answer at the question: Do we get the right quality of services caused by the product, as a result that it is fitting to the end-user.

These two definitions are different! That conclusion we made together when we read these statements.

I think these two statements are not definitions but “roadmaps” or “routes” of how we’re doing our work. In the picture this is the twisted line. And as you can see in the picture there are two lines with different colours.

Each line is different and this is caused by the background of different people. The tester has other knowledge; another role and other interest as for example our customer. The tester for example knows a lot about test approaches,  test design techniques and more While the customer has the interest to deliver the product in a specific time, to overwhelm the market.

I think that in what kind of role you’re having, the definition is equal. But the goal is shared, in terms of delivering an information system that fits the use and meets the requirements. Because of a background the route (twisted line) to reach this goal is different.

So realize that if you’re doing your work, there will be differences. But what more important is, there are agreements and there’s always a common goal. Try to figure out how this drawing fit in your situation.