T.E.S.T interview | 11
“Awareness of testing needs to be increased. Its crucial
place in the product lifecycle and how valuable it really is
need to be communicated. There is still a stigma attached to
testing. It is seen as a bottleneck in production that holds-
up progress. This is compounded by the fact that testing is
a relatively young discipline, managers say, ‘we didn’t do it
before, so why do we need to do it now?’ But if they want to
deliver quality products better and faster testing is a crucial
part of the process. ”
versus benefit versus quality. We have hostile to the concept. “It does
to maximise quality and benefit with have its place,” she says. “In the right
minimum cost. And this manifests place and time and in the correct
itself as risk-based testing, where the project and application it can be
issues that are most likely to occur very effective.”
are tackled first and those least likely Another potential challenge for
to be a problem are not immediately Europe’s software testers is offshoring.
prioritised. But some testing is always In an early testing job McCowan-
better than none.” In this way the high Wright had some experience of an
and medium risks are concentrated on offshored job and decided it was
and if possible the low risks are tackled not all it was cracked up to be.
if they can be within time and budget “Communication is key,” she argues.
constraints. “If communication fails it can be
catastrophic to a project, but this is
Automation and offshoring true for any project, people working in
Another way of tackling the different locations across the UK could
constraints of budget and time have exactly the same problems. Clear
is through automation, but Sally precise and timely communication is
McCowan-Wright thinks that it isn’t what’s needed and if the channels are
the answer in most cases. “Automation open then offshoring does have
has been pushed into testing its place.”
incorrectly in the past,” she asserts.
“Non-code-based testers are unable to Raising the profile
use and can find it hard to understand Looking ahead, Sally McCowan-Wright
the implications of what’s thrown up sees the need to get the message
by automated systems because the out. “Awareness of testing needs to
faults are generated out in code that a be increased,” she argues. “Its crucial
functional tester wouldn’t necessarily place in the product lifecycle and
understand. A lot of money has been how valuable it really is need to be
wasted because automated systems communicated. There is still a stigma
either were not needed, used or attached to testing. It is seen as a
maintained. It will never take the place bottleneck in production that holds-up
of manual testing because products progress. This is compounded by the
are very user-driven these days so it fact that testing is a relatively young
takes a human to spot faults.” discipline, managers say, ‘we didn’t
There is now a problem with do it before, so why do we need to do
scepticism about automated testing it now?’ But if they want to deliver
because systems were sold badly in quality products better and faster
the first place, but she isn’t entirely testing is a crucial part of the process.”
T.E.S.T | March 09 March 09 | T.E.S.T
Page 1  |  Page 2  |  Page 3  |  Page 4  |  Page 5  |  Page 6  |  Page 7  |  Page 8  |  Page 9  |  Page 10  |  Page 11  |  Page 12  |  Page 13  |  Page 14  |  Page 15  |  Page 16  |  Page 17  |  Page 18  |  Page 19  |  Page 20  |  Page 21  |  Page 22  |  Page 23  |  Page 24  |  Page 25  |  Page 26  |  Page 27  |  Page 28  |  Page 29  |  Page 30  |  Page 31  |  Page 32  |  Page 33  |  Page 34  |  Page 35  |  Page 36  |  Page 37  |  Page 38  |  Page 39  |  Page 40  |  Page 41  |  Page 42  |  Page 43  |  Page 44  |  Page 45  |  Page 46  |  Page 47  |  Page 48  |  Page 49  |  Page 50  |  Page 51  |  Page 52