Hi Andre,
André Schnabel wrote:
this (moving qatesttool scripts to CWS-process) has *not* been discussed
in Essen. We spoke about tagging testscripts so that they are in line
with MWS milestones.
okay, I just asked Helge if there are concerns about our way.
BTW - I never found, that having no CWS for testscripts did hinder me
from my (small) contributions to the testscripts. Having a CWS will
hinder me (as I'm not used to the process).
Small changes, yes. We are talking about complete features or UI changes
which also should be able to be done by the community outside Sun (one day).
Let me try to explain:
We have here machines for Mac OS X, Solaris x64, SPARC and
Windows which testing all the time the MWS. The problem: If a
CWS changes many things we have to change the test cases at the
moment *after* the things are integrated and the automated
processes will fail on all platforms.
With the change the scripts will be merged at the same time as
the software code will have a new install set. The test won't
fail because they are in sync with the software code.
So, maybe "tagging" is too short explained. We will be in sync with the
software code.
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]
