Hi,
Vito Smolej schrieb:
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...
I think, we really need to identify the tests that need to be run in an
localized environment (and therefore must support localization).
We will have automated localization testing at the agenda for next IRC
meeting ... I hope, you can join and tell your experinces.
At the moment I think, we would need three set of tests to support our
test process:
- one set to test the very basic funcionality of any build (means this
can / should be used on any platform or localization). At the moment I
think, first and topten test is enough for that.
- one set of tests to verify overall functionality that is not
localization dependend. I think, this could be the current
ooo_releasetest.sh .
- one set of tests to help localization testing. Actually I have no idea
what would fit in there. one usefull thing might be the create
screenshots script that has been recently submitted. (But just to take
the screenshots, not necessarily to verify the functionality)
André
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
