From: Helge Delfs <[email protected]> Subject: Re: [qa-dev] Re: testautomation missing "script" Date: Tue, 13 Jan 2009 06:41:52 +0100
> Hi Maho, > > Am 13.01.09 01:26, Maho NAKATA schrieb: > > Hi Helge and Andre > > > > I performed a test on WinXP+OOO300_m14+ja > > + > > http://ooopackages.good-day.net/pub/OpenOffice.org/qa/testautomation/OOo_OOO300_m14_testautomation.zip > > > > Some pitfalls from dummy... > > * as Helge told me, I need test list from the QUASTe site. > > http://quaste.services.openoffice.org/index.php?option=com_quaste&task=tests_overview&workspace=OOO300&milestone=m14 > > Helge:. > > I didn't find category 3 test list above, exact OOO300_m14.txt is below [1] > > . > > Hmm, don't know exactly what you mean. OOO300m14 should be of category 2 > normally (see [Tests required] section). OOO300_14 is OOo 3.0.1rc1, so it should be of category 0? > But as OOO300 is a release > branch only category 0 tests are required in this case (see [Tests > release] section) I see. > > Also, I think we should should have these lists in testautomation/global > > directory. > > something like following. > > OOO300_m14.release.txt > > OOO300_m14.category1.txt > > OOO300_m14.category2.txt > > OOO300_m14.category3.txt > > Should I raise as an issue? > > The file must then created during build process I'm not sure, but.. you have the original infomation and integrate "testautomation" module and then, should have this list, I assume it's easy...,though. > and this is not possible. It seems I still don't understand the process. > My idea was to have 1 file only and with category model you No problem and very nice! > don't need 3 files as before because you only have to test [Tests > release] + [Tests required] => tests for current category. > Maybe the file from QUASTe should have 1 additional flag to show if it > is a release branch or not to let the script know what tests must run. Okay. Best regards, -- Nakata Maho http://accc.riken.jp/maho/ --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
