Hi Helge, and Andre
thanks for your explanation.

I found "DEV300_m38/testautomation/tools/run_tests/run_tests.sh".
thank you very much.

Two questions...
First one is: 
Then, where the following ".lst" files? 
first_topten.lst
ooo_releasetests.lst
ooo_category1.lst
ooo_category2.lst
ooo_category3.lst
These lists are not maintained by you?
Andre, are you maintaing above mentioned files?

The second one is:
> As it was decided to add those scripts on
> DEV300-Branch one must use
> for 3.0.1 testing the scripts of
> ftp://ftp.ooodev.org/pub/qa/qatesttool_ooo240.tgz.
Sorry I didn't understand what you wrote.
Do we use ftp://ftp.ooodev.org/pub/qa/qatesttool_ooo240.tgz
for testing 3.0.1?

Best regards,

From: Helge Delfs <[email protected]>
Subject: [qa-dev] Re: testautomation missing "script"
Date: Mon, 05 Jan 2009 09:37:00 +0100

> Hi Maho (Happy new year to you also and to all reading this mail)
> 
> Am 05.01.09 09:19, Maho NAKATA schrieb:
> > Hi Helge, (a happy new year!!)
> > 
> > I'd like to ask you about my checkout of "testautomation" module.
> > 
> > I tried to test OOo 3.0.1rc1 on my WinXP and, testtool runs perfectly.
> > However, I cannot find "scripts" directory so that we can run all tests
> > of a specific category much easier. 
> > In ftp://ftp.ooodev.org/pub/qa/qatesttool_ooo240.tgz
> > scripts directory has some files:
> > 
> > % ls script/
> > CVS/                        ooo_category1.lst       ooo_releasetests.lst
> > analyze/                                    ooo_category2.lst       unix/
> > first_topten.lst                            ooo_category3.lst*      win32/
> 
> This was addressed in this issue 93675 and has been fixed on DEV300m37. See
> http://qa.openoffice.org/issues/show_bug.cgi?id=93675
> for details on this. As it was decided to add those scripts on
> DEV300-Branch one must use
> for 3.0.1 testing the scripts of
> ftp://ftp.ooodev.org/pub/qa/qatesttool_ooo240.tgz.
> 
> 
> Best Regards
>  Helge
> 
> ---------------------------------------------------------------------
> 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]

Reply via email to