Hi Helge,
Thanks a lot for your detailed answer. 

Screnshots are made to help translation to find out non-translated parts
>on dialogs and so on

>From your answer, Screenshot is for resource test, right? but how can we know 
>if it's correct, need take a look at these pictures by tester?

Cheers

-Xuefei



在2008-12-11,"Helge Delfs" <[email protected]> 写道:
>Hi Xuefei,
>
>Am 11.12.08 02:59, xduan_bj schrieb:
>> Hi All,
>> I'm a new member in OO QA and I'm learning automation scripts. There are 
>> many questions I want to ask... Thanks a lot in advance.
>
>Welcome to OOo Quality Assurance
>
>> 1. What's difference between qatesttool & testautomation module? Which one 
>> should I use when I want to test OO3?
>
>testautomation is used onOOO300-Branch and DEV300-Branch starting with
>m29. All prior branches are using qatesttool
>So if you want to run tests on OOo 3.x please use module testautomation.
>
>
>> 2. How can we check automation testresult pass or fail? one by one checked 
>> by reading log? or just from quastate website?
>
>Depends - you can use both ways to check your results of automated
>tests. When reading the resultfiles in testtool you have to open each
>resultfile one by one whereas In QUASTe it is easier and faster to check
>because the results are summarized and the results are shared and can be
>viewed by others. For a deeper look on testresults and debugging it is
>always better to check the resultfiles in testtool directly.
>
>> 3. I found a script directory under qatesttool module and there are two 
>> batch files to run these automation scripts(releasetest & screenshot), we 
>> need't test all of automation scripts? just a subset is ok? what rule should 
>> we follow when defining the subset?
>
>Currently tests run on base of 'category model' See following wiki page
>for definition:
>http://wiki.services.openoffice.org/wiki/QUASTe#Category_model
>Screnshots are made to help translation to find out non-translated parts
>on dialogs and so on
>
>
>> 4. If I want to learn how to writing scripts by myself and want to 
>> contribute some scripts to qatesttool module, how can I grasp it quickly and 
>> which testarea need add new scripts?
>> Your guideline&suggestion is very important to recruit, thanks a lot for 
>> your help!
>
>From my experience the best way to start is running some automated tests
>first to get some feeling how they work and what to do if something
>fails. Get friendly with the already written code and start debugging in
>case of errors. Of course reading documentation on how it works is also
>important. Chum up with testtool and tooling around testtool (QUASTe,
>scripts and so on)
>
>Some links:
>OOo Automation team pages
>http://qa.openoffice.org/ooQAReloaded/AutomationTeamsite/ooQA-TeamAutomation.html
>
>Testtool Quick start:
>http://wiki.services.openoffice.org/wiki/VCLTesttool
>
>QUASTe documentation:
>http://wiki.services.openoffice.org/wiki/QUASTe
>
>
>Hope this helps...
>
>
>Best Regards
> Helge
>
>
>-- 
>===============================================================
>Sun Microsystems GmbH           Helge Delfs
>Nagelsweg 55                    Quality Assurance Engineer
>20097 Hamburg                   OOo Team Lead Automation
>http://qa.openoffice.org        mailto:[email protected]
>http://wiki.services.openoffice.org/wiki/User:Hde
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: [email protected]
>For additional commands, e-mail: [email protected]
>

Reply via email to