Helge: Is there an effort to move the test scripts from German to English? I have enough familiarity with the testtool program (after attempting to find out a bug in the Mac Intel build) to attempt to do this, but I don't want to duplicate efforts by the Star Office folks.
Thank you (Danke!) James McKenzie -----Original Message----- >From: Helge Delfs <[EMAIL PROTECTED]> >Sent: Feb 28, 2007 8:11 AM >To: [EMAIL PROTECTED] >Cc: [email protected] >Subject: Re: [qa-dev] re /qa/qatesttool/ scripts summary in perl > >Hi Shaun, > >Shaun McDonald wrote: >> I would love to see such a tool to be produced. I would love to be able >> to upload a zip file of all my testtool results and compare them to >> everyone elses testtool results. >> I would be able to help towards this project, however until I graduate >> in July, I don't have much time to spend on the OpenOffice.org project. >> However I could set the ball rolling, by starting to design the system >> on the wiki. > >pleasent to hear that you are interested and willing to help the >community start creating such a valuable project. As you may have read >on the list I was the initiator and developer of a project named >'QA-Statuspages' inside SUN to have all our results of automated tests >collected and evaluated. I would like to give a quick overview of what >we think the requirements should be met to realize such a project as >measured by our experience. > >1. Hardware >A server running a webserver, database-server and has scripting enabled. >Maybe SAMP or LAMP (depends on your OS) > >2. CVS >This server should maintain a complete tree of automated tests from CVS >and should be updated in a (to be defined) time range to have always an >up-to-date state of all testscripts > >3. Database >A database server to host the data would be the best to work with, >because there will be an amount of data to be collected. As announced >some time ago, I would appreciate to make our database model available >to the community. We use mysql. > >Some maybe helpful suggestions how our environment works. > >- All information about testscripts (bas- and inc-files, testcases, >subs, documentation and so on) is collected and processed by a script >and committed to the database. (point 2.) >- All testresults and -information of automated tests are processed by >testtool, written to text-files and committed to the database. For >further information see documentation in testtool-script >'qatesttool/global/inc/status.inc' This file is responsible to collect >and process data created during automated testrun. There will be a >script needed to submit collected data to the database. > >Now you have all information needed to create pages to evaluate testresults. > >Some features of our environment: >- Testresults grouped by platform >- Testresults grouped by application >- Testresults for pre-selected application >- Detailed testresults for a specific autotest >- Detailed testresults of a specific testcase >- Documentation of a testcase >- Compare results of automated tests in CWS with results from MWS >and so on. > >I hope I was able to give you a short overview and some tipps to make it >easier to start this project. If you have any questions don't hesitate >to ask. > > >-- > Best Regards > Helge > > > >--------------------------------------------------------------------- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
