Status of "How To localize testtool environment"

Hi *,

I'd like to give a short status update for the wiki page:
http://wiki.services.openoffice.or
g/wiki/HowTo_localize_qatesttool_environment

The page lists the steps you need to get a working testtool
environment 
for your localization. An the page tells *only* about
localization, not 
about OOo vs. SO environments or different platforms.

The page covers some initial tasks (I think, they are
complete) and the 
tasks to get the update tests running. For the update tests
only the 
framework tests are not completed yet. Although I was able
to run those 
tests on a vietnamese build, I still need to document the
results and 
file some patches. Unfortunately I will be busy with other
things 
withing the next weeks or even months, so this may take a
while.

I would suggest, that some localization teams try to go
through the 
steps and localize their own testtool environment. I hope,
that the wiki 
page could be verified / improved that way.

Some hints for the work:
- don't  create just the files / patches as written in the
wike. Try to 
*understand* what you do.
- run the testscripts step by step and learn to read the
logfiles
- create small patches that cover a single area (each area
has a 
maintainer - if only one maintainer needs to review your
patches this 
will speed up the work)
- If you like to get a quick response don't ask if a release
date is 
near (people will be busy doing release tests 
- have an english OOo at hand, to verify if problems are
caused by your 
localization or if they occure in a non localized build as
well
- If you have some time read 

http://qa.openoffice.org/qatesttool/OOo_testtool.pdf

Problems I see:
- Although the scripts are well maintained they have errors.
For 
somebody who likes to focus on localization issues only it
is very hard 
to tell, why the errors occure.
- The scripts are written for StarOffice in many cases.
There is code 
for OOo as well, but not that well maintained.
- People working on OOo often do not know about a StarOffice
environment 
and vice versa (so a change that would be good for OOo might
break test 
cases for SO)

I still think, we need to identify some tests that do not
realy need to 
run in localized environments. Having "all tests
running without errors" 
is a nice theory but will cause a lot of work. And this is
not only the 
initial work, but ongoing maintenance.

André

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribeqa.openoffice.org
For additional commands, e-mail: dev-helpqa.openoffice.org

On 28 Feb 2007, André Schnabel told this:

> I'd like to give a short status update for the wiki
page:
> http://wiki.services.openoffice.or
g/wiki/HowTo_localize_qatesttool_environment
>
> The page lists the steps you need to get a working
testtool
> environment for your localization. An the page tells
*only* about
> localization, not about OOo vs. SO environments or
different
> platforms.

André,

thanks a lot for this wiki page. I spent some hours and
almost finished
with inputs for Russian. Next is Turkish. Very helpful page
and now I
know how to avoid a lot of warnings in automatic tests. ;)


-- 
Best regars,
Rail Aliev
http://{ru,tr}.openoffice.org

	"What time is it?"
	"I don't know, it keeps changing."

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribeqa.openoffice.org
For additional commands, e-mail: dev-helpqa.openoffice.org