Hi!
It's nice to see that the interest on using the VCL TestTool is growing.
Thank you very much for your comments, suggestions etc. Be sure, we
read it and we answer! And we need your input!
The automated testing team inside Sun Microsystems maintains at the
moment 100% of the testing code but there is hope that also others will
start writing test code in future which can be also shared and used by
others. That would be a great test case development.
To get you into the boat we want to get a good set of test scripts [1]
and will do some enhancements in these areas:
1. Documentation
2. Reuse
3. Structured
4. Mainenance
We know for 1.) that we need to document how to add a new L10N language
to the framework and also we need to make it easier (4.).
_Do you_ have suggestions for the other areas we should think about?
If yes, feel free to write here an answer. We want to collect in the
next three weeks which enhancements we need to to do to get the barriers
down and you into the boat. I will summarize it and maybe you are alos
interested to do some work with us...
Thank you in advance for supporting OOo!
Cu,
Jogi
http://qa.openoffice.org/qatesttool
http://wiki.services.openoffice.org/wiki/User:Jsi
_____
[1] Software Test Automation, Mark Fewster & Dorothy Graham, Addison
Wesley, 1999, ISBN 0-201-33140-3, page 69; table 3.1 "Comparison
of good and poor sets of test scripts that perform the same set
of test cases"
--
===============================================================
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]