Specs? oh well (crimson ears) : XP home, running on a notebook at cca 2 GHz.

Seriously, I would like to get ALL res files, so that I can tinker with feature extraction.
What I've seen so far is a PERL (!!) script to create summaries. Huh?!

So what I indend is a little excursion in UNOland, so that I could offer an ODT file or something similar that does it. If somebody else already has done it, even better
- let us have it.

Also, if I had all RES files with warnings etc I'd assume I could localize completely, not just within the sanity case. Plus I'll collect some experience on the way - to keep
others from falling into this trap for instance.

Regards

smo

Regards

James Mckenzie wrote:
Vito:

System specifications please?

This is a full on run and may take a week to complete.

James McKenzie


-----Original Message-----
From: Vito Smolej <[EMAIL PROTECTED]>
Sent: Jan 5, 2007 5:00 AM
To: [email protected]
Subject: Re: [qa-dev] Testtool & TCM - OOoTestRun32win runs N runs N runs...

a note of caution:

my OOoTestRun32win for 2.1 has been running >>for the last 72 plus hours<< and it's still bulldozing on. Right now it's doing the docbook_losa.bas I am already beyond the "this-cant-be-true" level. I'll send an "I DID IT" T-shirt to anybody who can prove (bar the sun core group) to have persisted all the way.

Asking for automation in my of earlier posts- hurrumph... there's quite a lot of it already available. More than enough? Much more than required?

Regards

smo
Santiago Bosio wrote:
It is me, again...

First of all, I want to thank Rafaella, Naoyuki, Petr, and Andrea for granting me the necessary permissions to start working on QA, and their recommendations.

We used TCM to do our first tests, in order to familiarize ourselves with the QA process, without problems. But we have a BIG question: What to test?

Our current objective is to have an approved Spanish version, that leaves the RC status. So: we have to do ALL tests? Or it suffices with tests on realease sanity scenario? IMHO we have to focus on tests that can assure us that the build is mostly functional and thus, could be approved, but as we are QA beginners, we don't know which ones they are! :-P.

OTOH, there's Testtool. I've configured it, and run some tests on it. It seems promising, but again: I don't know what to test first. My guess is trying the script ooo_releasetests (both for win and linux). Another doubt: how it relates with TCM? I see that Testtool performs more tests than those on TCM, but I suppose it doesn't supersedes TCM (things like "check that all strings are correctly translated" can't be tested with testtool, for instance). There's a relationship between Testtool results and TCM results?

I told you I will ask too many questions...

Thanks in advance,

Santiago.

---------------------------------------------------------------------
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]


---------------------------------------------------------------------
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