Hi NAKATA,
thank you for a view into your workflow and the tools you use.
NAKATA Maho wrote:
> Doing QA is a pain,
Is it? I think not. Also automated testing what you mentioned later in
that mail is not a pain.
[I have seen the smily at the end in the original sentence but other
readers could understand it different/wrong, so I write down my
personal words why QA is NOT a pain, ok?]
A QA member should IMHO understand that he is always trying to protect
users work[flow] with the product he is doing QA for. That is his job.
If only QA team fails using the product it happens once a time and the
development is able to fix it "in time". If users will find the same
problem it maybe will happen many times and maybe they won't use the
product anymore because there is nobody who would fix the problem "in time".
Doing QA is a destructive work[process] because your goal is to destroy
the [creative] work of others and you always have to view from "the
other side" than the creator of a work - who is thinking that he has
donw the work well. The creator of a piece of software is thinking 'I
have done everything to avoid mistakes' and he is right. The tester is
trying to VERIFY that this view is not just a whish. It has to be the
truth also in other contexts than the creator has thought about. His
thinking is different: 'Did the creator really everthing to avoid mistakes?'
If you want to move destructive work to creative work you have the
chance in modeling/enhancing the QA processes, documents, ... to help
others to get their work easier done in less time. WRITING automated GUI
tests is a one possibility to get a creative part in the <destructive>
QA process. So automated testing is not a pain - it is a service to
testers to get stupid work done and in the meanwhile the tester can do
creative work. Not all testcases are good for automated testing but the
ones which go on your nerves every realease are often a good candidate
for being automated...
As you can see: Doing QA and automated testing must not be a pain. It
depends on that what you understand as QA/Testing.
Thank you for supporting [the users of] OpenOffice.org!
Cu,
Jogi
--
===============================================================
Sun Microsystems GmbH Joerg Sievers
20097 Hamburg Quality Assurance Engineer
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
