qa
|
| Subject | [qa-dev] re /qa/qatesttool/ scripts summary in perl |
|---|---|
| Response to | [qa-dev] Re: [qa-cvs] CVS update: /qa/qatesttool/script/, /qa/qatesttool/scr (James McKenzie) |
| Standard display | Raw display |
|---|
From: Thorsten Ziehm <thorsten.ziehm@sun.com> Date: Thu, 22 Feb 2007 12:47:45 +0100 Content-Type: text/plain; charset=windows-1252; format=flowed Subject: [qa-dev] re /qa/qatesttool/ scripts summary in perl
Hi Vito et all, > My suggestion is (still) to have somebody from the SUN team write this > up as a BAS and add > the result to the testtool. > My suggestion is still to get a portal inside OOo, where all TestTool results are collected. Then a comparison is possible between different platforms, languages and versions. Only this bring the feedback you needed. If you run a test with 20 errors and 50 warnings, does not say anything. Because all tests should run without any error! Each other result needs analysis, and this is only possible with a comparison in such a database or with the result files of the testcase. And as I often wrote, the resources in Sun QA are very limited. We will provide a mentor for this project, but the work have to be done by the community. This was a project at the last Google Summer of Code, but it wasn't accepted. Then it was discussed on last OOoCon in Lyon and after that it doesn't have any priority. So if you need such tooling, find someone who can realize this project. Thorsten
Responses
| Date | Author | Subject |
|---|---|---|
| 2007-02-22 | Shaun McDonald | [qa-dev] re /qa/qatesttool/ scripts summary in perl |
