Hi Maho,
Maho NAKATA wrote:
2. VCL testtool problem.
Assume MacOSX team's resouce is rich enough to do every CWS QA.
VCLtesttool script is not solid for outside of Hamburg team. Can you reduce
the number of errors to zero? No.
See also, Andre's issue http://www.openoffice.org/issues/show_bug.cgi?id=74868 .
(That's why I'm interested in this tool too.)
it won't be ever that we have consistantly 0 problems in a testrun. It's
the same as a developer never will write code with 0 defects. Accept it
or not it is the reality.
So, we didn't define the goal 0 problems in test scripts ever! We
defined <5% to get the analyze of the less problems done in a economic
timeframe.
The goal is that a QA member will be able to analyse a minimzed count of
problems if they occour on environment dependent or _s_oftware _u_nder
_t_est (SUT is here OOo) dependent reasons.
What we do here?
If a testcase (not a whole test!) fails....
1. Run the testcase seperately
2. If the problem exists it is a problem
2.1. ...of the software under test (SUT)
You found a bug!
2.2. ...of the test script
You found a test script bug which has to be fixed by
your own or a test script writer (e.g. the maintainer
of the code)
3. If the problem does not occour...
3.1. run the same sequence of test cases in front of the problematic
test case to see if the problem is dependent on the runtime of
the SUT.
3.1.1 You could find memory leaks at runtime.
3.1.2 You could find test script problems which do not reset a status
in another test case which is needed by the problematic test case
3.2 You found a temp problem with your environment (network, memory,
other applications)
What is important?
Do NOT use the display/same system for other work! The office will get
the focus to work on menus, dialogs, etc.!!!!
Hope that helps... more than flame wars (which will be ignored by me, be
sure; Sun is a part and founder of the OOo open source community and we,
the employees are willing to help as best as we can and earning flame
wars is not part of any job description here. Thank you)!
Cu,
Jogi
http://qa.openoffice.org/qatesttool
http://wiki.services.openoffice.org/wiki/User:Jsi
--
Sun Microsystems GmbH Joerg Sievers
Nagelsweg 55 Quality Assurance Engineer
20097 Hamburg
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
