The Agile Testing Manifesto. Part 2

The Agile Testing Manifesto. Part 2
In this article we will continue our analysis of the Testing Manifesto written by Samantha Laing and Karen Greaves with the next principle:

We value building the best system over breaking the system.

I’m reminded of the joke below when I read the principle above:

A tester comes to a job interview.
When he enters the room, the interviewers point to a chair and say, “Sit down, please.”
The tester sits down on the chair, and it breaks under him.
“You are hired!”

The anecdote might be funny, but it is far from reality. Although there is a common belief that testers are exclusively engaged in destruction, it is only half true.

Agile Testing in Software Testing

In fact, many people in that profession like to break something and are fond of finding defects. Yes, a tester can play the role of an evil-minded user and try to destroy something, but this is only one of numerous aspects of the job.

Positive testing is no less (or even more) important than negative testing. Sometimes, testers, especially beginners, are too enthusiastic about complex negative tests: What if you enter 15 fraction digits? What if you enter a string of 5000 symbols? What if you send a message consisting of all special characters, like that: "~!@#$%^&*()_+{}:;'`"?><[]"? All that is very fascinating, but one should remember the main goal – to create a product that has a certain value and performs its functions as intended. That is why simple positive tests such as reproducing a users’ actual actions are of top priority.

We value team responsibility for quality over the tester's responsibility.

Generally speaking, the entire team’s responsibility for quality is a fundamental principle of Agile.
But how many team members feel that shared responsibility? When some problems arise, what do you and other members of your team do? Try to prove that someone else is to blame, or you think, “What could I have done to prevent or correct it?”

If there is a problem with quality, do they blame testers alone or do all team members share the responsibility?

Authority and Responsability in Software Testing

Actually, testers cannot improve quality, their role is to determine the level of quality and inform the stakeholders about it. You can only improve quality by joint efforts of the entire team.

Victoria Slinyavchuk
Consultant on Software Testing

Share the knowledge