zhang Hong schrieb:
> Hi all,
> 
> In directory "qatesttool\errorlog", there are two .txt files: dummy.txt and .
> 1. Who can tell me what are the two files?

dummy.txt was just for technical reasons, to create the directory
'errorlog' on cvs checkout. Usually empty directories are not created on
cvs checkout.

'.' is not a text file. It's just 'current directory' in unix speak.

> 2. When I enter in directory "qatesttool\errorlog" form QA CVS (current tag 
> is DEV300_m10), 
>    
> http://qa.openoffice.org/source/browse/qa/qatesttool/errorlog/?only_with_tag=DEV300_m10
>    After the file privateenvironment.txt, I read a note: CHG: Quaste 
> preparation - enabled now for OOo. 
>    Does the file "privateenvironment.txt" has relation with Quaste ?
>

privateenvironment.txt controls 2 things:
1. It points to a custom directory tree, where special parameters and
informations are stored, that are needed in local test environment.
We host the testscripts localy for all testers and put there special
serverinformation and access data into it that is needed for some tests.
the public data mirror is in qatesttool/global/private.

2. It controls the behaviour of how the test result is treated:
0: automatical submitting status; filespace location defined in
privateenvironment.inc
works only inside Sun Microsystems Hamburg environment
1: automatical submitting status; filespace location defined in testtoolrc
works only inside Sun Microsystems Hamburg environment
2: manual submitting status from errorlog directory
In the errorlog directory a directory is created based on OOo version, like:
dev300m12, where .txt files are created for every test;
you zip this directory and upload it in QUASTe
this is the Default setting for 3.0

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]

Reply via email to