Thank you. Yes the below information are very useful.
Rafaella
Andre Schnabel wrote On 12/04/06 19:12,:
Hi Rafaella,
Rafaella Braconi schrieb:
Hi Andrea,
TCM and QATrack are obviously 2 different tools. What you are
suggesting is to
a) use TCM for testing purposes only and
b) use the QATrack tool to approve the tested builds.
Is that correct?
correct.
I'd like to add, that the tools have (had initially) a different focus:
TCM's focus is / was manual localization testing. TCM is more intended
to hold single test case descriptions an manage them.
The idea behind QAtrack is to replace the (manually maintained)
localization status page and give a tool for some of the stages of the
release process. Starting from notifications that binaries are
available ... tracking, who is doing tests at all .. to final approval
and moving the builds to the mirror network.
Esp. collecting the informations, where the builds are available is a
problem.
Also, in the wiki you are talking of getting the QATrack linked to
TCM. Can you please let me know which are the specific requirements
for this?
First possible link is user management (the dream of a single logon
for all the OOo related tools).
Another idea is to link to a TCM report from within QATrack to verifiy
the approval of a given build.
Hope, that answers some of the questions.
André
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
