Hi E'body:
I got myself the current state of qa/qatesttool and - regarding the use
cases
i) it's different from the previous - (well, it better ;), and kudos to
developers)
ii) it tests OK on 2.1, at least as regards first and topten
iii) it shows some flexibility as regards unexpected strings, that the
system tested provides
So one can assume that downloading the latest version would be all it
takes to start on 2.2.
Regarding the BAS (i.e. the code) it still does not know anything about
slovenian language - not that it would be that TERRIBLY important.
Maybe this will turn out to be my first commit;)
Regarding the subjects to be tested in language versions: If the
testtool is thought of as a generic customer, it's supposed to use/run
the program the same way, whatever the language version (it just happens
that it needs to be polyglotic now and then...). So all the test
routines, intended for EN, should be a valid ammunition for localized
versions per default. Either they would run (fine) or they would not
(fine as well, one more issue, that happened to avoid the net so far).
Of course I must be overlooking something very evident (g).
Regards
smo
James Mckenzie wrote:
Vito:
I think your point is that the testtool scripts from 2.1 do not work with
2.2rcXX. This is quite possible.
Thorsten:
Are there going to be new testtool scripts for 2.2?
James McKenzie
-----Original Message-----
From: Vito Smolej <[EMAIL PROTECTED]>
Sent: Jan 25, 2007 3:01 PM
To: [email protected]
Subject: Re: [qa-dev] TestTool: which scripts to use to test OOo 2.2 (RC)
Running the existing test cases (well, those, I could lay my hands on
lets say in November) I found quite some errors, not in the localized
build, but in the qa/testtool itself (see issues 73777 and there
around). My question was simply , what's the best way for me to be
still useful , given the fact, the testool routines evidently keep
changing - beside the product of course.
Given your point that "... we are testing OOo and don't want to test the
TestTool..." it looks rather like Im in the wrong lane;\ Yogi, tell me
it's not so...
Regards
smo
Thorsten Bosbach wrote:
Vito Smolej wrote:
Hi Thorsten:
Can one use the new testtool on 2.1? I would not like to beat a dead
horse with my l10n reports on possibly outdated testtool AND build.
The best of course would be to have a localized 2.2 ... In case it
takes time, I can try to be useful by tusing 2.2 testtool on the
(outdated) localized 2.1. If it makes sense of course - if it does
not, I can at least spare the bandwidth;)
I currently don't see the point?
What do you want to do?
Testing the already released OOo 2.1?
Testing the upcomming release candidates for OOo 2.2 aka OOF680mX?
Please define 'new TestTool'.
The release of OOo 2.2 will happen with the current TestTool.
Or to be very correct the TestTool from SRC680m50.
(The one that is available for download for some platforms at
http://qa.openoffice.org/qatesttool)
Ok , in OOo builds you find also a TestTool, that may be used.
But there might be unknown errors, since it depends on OOo Basic,
which changes during the builds. And since we are testing OOo and
don't want to test the TestTool I recommend using the one from
SRC680m50 if it is available for your platform and works.
If you have a working environment for your TestTool it will work for
every version of the TestTool!
The point is to get one time used to running tests.
cheers
Thorsten
TiA for advice
smo
Thorsten Bosbach wrote:
Hi Testers,
to test the release of OOo 2.2 please checkout/update your
scripts with the tag: ooo220
The scripts are currently worked on.
So you should update your scripts once a week.
The HEAD will now be used for SRC680 changes.
See also the wiki page about available tags.
http://wiki.services.openoffice.org/wiki/Cvs_tags_and_branches
cheers
Thorsten
---------------------------------------------------------------------
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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
