Hi! Mechtilde wrote: > the Problem I see is that these member of the (Community)-Qa who use the > testool to get e.g screenshots for the UI localisation-test or testing > community builds aren't involved in the developing process.
If you use a tool to get these screen shots it would make sense to see the ongoing progress (it is not very often that we change it but sometimes we have to adopt processes on the development behaviours). > But if I have to change my testing environment that is very important. Who/Where it was described to you how to use the tool? Ask him to docoment it with the changes we have done now. > In the title of the mail you wrote I can't find any hint that there are > results of a process and that the tester have to change their environment. > > <Citat>[qa-dev] [AUTOMATION] Modul testautomation will be part of the > CWS process from </Citat> The CWS process is well documented and should be known by every tester in the testing team. (Also by L10N etc. because changes in the product only can get in with a CWS). The 'testautomation' will follow these processes now to have _one_ and not two processes. If you have a documentation issue about how to use the testtool now, write an issue. 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]
