Hi Vito, Vito Smolej wrote:
maybe you can find some use for the complete errorlog - compressed here - from releasetests slovenian 2.2. I did the first few issues as you may remember, but possibly it makes more sense to do it in one sweep. Let me know, what makes it easier for you guys up in the north.
I have no resources to analyse every L10N-build rsults. My goal is to make it easier to enable L10N in automated test scripts. IMO there is a need to learn how (common) automated testing works in the basics. Sorry, but I can not do the work for an L10N team. We only can deliver the environment to be better and faster in sync with the rest L10N builds. Ok?
If you find a script part which has a problem with a language, write the owner of the file (maintainer) an issue (look into the file directly where the error occoured with a double click in the testtool result view).
Collections of archives making no sense - especially in mailing lists. We are more than one employee working on thousands of lines of test code....
btw, I dont have your macjogi email, hope its still OK.
That's only for the Mac OS X builds my private engagement, not for L10N. porting.openoffice.org/mac -> James is working on Mac OS X INTeL which I
do not have right now. Cu, Jogi http://qa.openoffice.org/qatesttool http://wiki.services.openoffice.org/wiki/User:Jsi -- =============================================================== Sun Microsystems GmbH Joerg Sievers Nagelsweg 55 Quality Assurance Engineer 20097 Hamburg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
