Hi Uwe,
good points.
Uwe Altmann wrote:
But TCS pages are clearly structured by OOo versions. So you have
testcases declared for every OOo version which seems to imply that this
is concerning this versions release test? Or is this just "Add these
cases too from this version on."
Yes and that is okay.
Or is there a kind of intelligent sorting on
http://qa.openoffice.org/ooQAReloaded/TestcaseSpecifications/ using the
"Valid for version:..." header in each test case to build a full
collection for the chosen version?
Some explanation:
The test case specifications are stored here at Sun in a database and
what you see is not the intelligence which the front end has. We are
working - as we have said on OOoCon - on open sourcing the tooling and
then you will see that you can priorize test cases on which milestones
they have to run and which are less important - for each test case.
I agree, that if we have the complete tooling public we need to talk
about syncing those tools. The TCM is good for L10N, the system we use
is good for ongoing, priorized testing inside an engineering workflow.
The step was to have the test cases first in the public that everybody
is able to help and to find issues. The second step is to have the test
case design front end public on a public server.
Now more clear?
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]
