Hi Uwe,
Uwe Altmann schrieb:
Hi Jogi
Thanks a lot for the explanation (and setting the right topic :-*) ).
Joerg Sievers schrieb:
But another thing it seems I've missed: What is the relation between
these test cases and TCM testing? Just replacing? Adding on?
TCM should be able to use the test case specifications. TCM is a
_management_ tool that some test cases has to run to a specific time.
The TCS (test case specifications) describe how to do a test case not
when or who.
There is AFAIK no relation at the moment between them but it would make
sense.
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."
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?
In my opinion the links behind the TCS section for each application team
inside QA-project should be changed. It is possible to link directly to
the testcases for Spreadsheet etc. It isn't needed to go throw the
versions etc. But then it must be possible to get all test case
specifications, which are valid for the latest version. And as I know
the processes for TSC uploads works like this. I think the spreadsheet
project is a good example for a collection of test case specifications.
So in my opinion we need direct links in each application team to the
collection for the current test case specifications. But we need also
a link for general TSC where you can go through the versions and after
that through the applications.
Thorsten
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
