That is, the quality is inherently subjective. And there are plenty of people who are affected by the software we produce ... With this in mind that a tester makes it difficult to stay focused when so many people with opinions that might matter, but if we know "that matters" We decrease the number of possible values for concern. However, this leaves us with several important values to be taken into account when testing the product.
So how can testers agree with that?
You could make an RPG when tested and put on the hat of another person during the trial period, or may allow the actual users to test the product and let them have something to say about what they find.
But for an expert tester is more about being subjective and multidimensional that several people at once.
This means that a lot of values, beliefs and preferences are taken into account that could be important. Not as a means but as several independent dimensions of quality that has (more or less) important. The hard part is knowing when a value is threatened and for which (type of) a person who is affected, and whether this matters at all.
Much of this happens automatically for many of you out there qualified testers, and when I thought I recently realized that this is something we do more and more and I hope I'm improving this skill every day. This is a great skill that when the trial software!
Anyone who has any ideas about this?
Have you experienced yourself?
If not, it does sound like something interesting to discuss? Would it be helpful to you?
0 comments:
Post a Comment