Hi Jogi, *

Thanks again.

Joerg Sievers schrieb:
> 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.
> 
Imho exactly this could be an excellent help for release testing too.

May be TCM is "just" for L10N testing by now, but this depends only on
the defined test scenarios available. So someone could easily define a
"2.3.1. release test"-Scenario.
The other way round one could put all these TCM test cases into the TCS
database too.

So I rather understand that TCS is a provider for test case definitions
which then can be used to define test scenarios and trace their results
 in TCM. Similar as you may do now with your internal TCS frontend.
Replacement of TCM by this frontend may be a suitable way too. Having
two tools for the same purpose will be not such a good idea.


> 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.

You need not to have the tools in open source to make their usage public :-)


> 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?

Yes I see. My starting point was that I didn't understand why you didn't
develop/integrate TCM tool to this but create a new tool parallel to that.
Just my 2 cent. We must not discuss this any further - work is waiting.
Thanks again for your explanations.

-- 
Mit freundlichen Grüßen

Uwe Altmann

OpenOffice.org auf dem Mac:
http://porting.openoffice.org/mac/

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to