Tuesday, 1 March 2011
In my experience, more testing and questioning of the spec before we get started vastly reduces the number of 'oh, we didn't think that bit through' occurences later on.
Unfortunately, it is not always easy as a tester to get in on the action at the spec stage, and we are often considered as an annoyance rather than a vital part of the team when we try to get involved. There are vague discussions about the spec, but nothing concrete, nothing written down, and then suddenly the software engineers have started coding, and yeah, the spec will be along in a bit.
So if anyone has any ideas about how to get in there sooner, and to be taken seriously at the concept stage, I would love some advice.
Friday, 18 February 2011
Nah... I don't really mean that. Sincere apologies to anyone who might be offended by my sexist title. I thought it sounded snappy :)
I don't think men & women test in different ways, but I definitely think that there's a big difference in the way that different people test. Where I work, we have quite a large group of testers, and the approaches my colleagues take are noticably different. If we all tested the same piece of software independantly, I'm sure we'd all find things the others did not find. It would be interesting to put that to the test, on one of those Testing Challenges you see around.
I think there are 3 main breeds of tester, although most people belong to more than one of the testing ethnic groups: