Bonjour,

Je vous forward ce mail pour mémo lorsque nous ferons le point du testtool.
Pour info, dans le programme du Google summer of Code est intégré le développement d'une base de données capable de manager le résultat des tests du testtool.
Plus d'info ici :
http://wiki.services.openoffice.org/wiki/SummerOfCode2006#Testtool_Result_Tracking_Tool

A bientôt
Sophie

-------- Original Message --------
Subject: [qa-dev] TestTool: which scripts to use to test OOo 2.0.3
Date: Thu, 11 May 2006 19:06:15 +0200
From: Thorsten Bosbach - Sun Germany - QA-Engineer <[EMAIL PROTECTED]>
Reply-To: [email protected]
Organization: Sun Microsystems
To: [email protected]
Newsgroups: openoffice.qa.dev

Hi,

to prevent the guessing on which CVS tag to use for testing
the upcoming release of OOo 2.0.3 here are some hints...

StarOffice Quality Assurance department at Sun Microsystems, Hamburg,
is currently starting to modify the test scripts CVS module:
qa/qatesttool

This includes putting WarnLogs (orange messages) on errors, that need to
get fixed for OOo 2.0.3, and changing WarnLogs  to qaErrorLogs (blue
messages) for issues, that are known, but won't get fixed for OOo 2.0.3.

The Format of known issues in the result file is:
#i12345# some description
or
Warning: #i12345# some description

If we are finished, there will be the announcement of the
CVS tag 'OOO203' in this newsgroup ([email protected])
We expect to be ready about 06.07.2006

Until then it is best to use the top level checkout aka HEAD.

cheers
Thorsten

--
*******************************************************************
Thorsten Bosbach                             Sun Microsystems GmbH
Quality Assurance Engineer                   20097 Hamburg, Germany

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




--
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.1.392 / Virus Database: 268.5.6/336 - Release Date: 10/05/2006



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

Répondre à