Hi all,
(just for coordinating the discussion: please answer to [EMAIL PROTECTED] only.
l10n and native-lang lists are cc'ed for information only here).
as mentioned at the qa list, last weekend several community members had
the chance to see a presentation about the OpenSolaris TCM. The tool was
intrododuced by Petr Dudacek and Petr Hruska who showed the TCM "in
Action" and could answer many of our questions.
The outcome was, that the OpenSolaris TCM would answer many of our
wishes and the enhancements would help to improve our testing process.
So we would like to go on and start migrating to the OpenSolaris TCM.
I have set up a wiki page for coordinationg the migration at
http://wiki.services.openoffice.org/wiki/TCM_migration
This is only a draft for the moment. You are welcome to comment and help.
Migration would be a joint effort of the Sun g11n, Sun QA and community
QA teams. Sun g11n team will start to review current test cases for
incorrect descriptions.
Within this time, we (community) should think about the next steps. E.g.
all current TCM managers should check the new TCM functionalities and
prepare the teams for the move. Please request a login to the
OpenSolaris TCM (if not already done) and take active part in the process.
Related to to this is the definition of test plans. The current
situation of two sources for test plans (smoke tests on the website and
test cases in TCM) is far from being perfect. As smoke tests are
outdated, they would be marked as such and should not be used anymore.
There are several test plans available in the Sun QA team. These are
mainly for testing new features and more complex than those curently in
TCM. At the moment we are looking for a good way to make those Testplans
available but have the option to coordinate the tests within TCM. It has
been suggested to have the complete testplan at the qa website and have
it as a test item in TCM.
As always .. comments and help is welcome.
André
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
