Hi Stephan,

> I just embarked on a new project, namely to clean up and consolidate the 
> various test frameworks and corresponding tests available in the OOo 
> build environment.

That#s highly appreciated!

> - The so-called "UNO-API" and "Complex" tests.  These are located in 
> */qa/unoapi and */qa/complex, use OOoRunner from qadevOOo, and can be 
> executed via cwscheckapi or checkapi.

Not sure whether you mix things here, or whether I am simply not
up-to-date: To my knowledge, the complex test cases in */qa/complex are
not (read: cannot be) executed by (cws)checkapi. At least in all modules
I now, they're accompanied by some makefile which allows to invoke them
via "dmake run" or some such.

> ...
> I know that this picture is not perfectly realistic, and that there will 
> be obstacles along the way that require pragmatic workarounds.  Still, I 
> think it is important to know what the ideal should look like, even if 
> you have to deviate from it.

Agreed. I'd already be very happy if only some parts of this could be

For the records, since you didn't mention it explicitly, though I think
it's on your list: (Un)Reliability of the tests is another major blocker
for their acceptance currently. Of course, in places where this is due
to the concrete test, not due to the test framework, this is to be
solved one by one only. But we shouldn't forget this important goal: If
tests do not run reliably, then the best test framework of the world
won't get us anywhere.


- Frank Schönheit, Software Engineer         frank.schoenh...@sun.com -
- Sun Microsystems                      http://www.sun.com/staroffice -
- OpenOffice.org Base                       http://dba.openoffice.org -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

To unsubscribe, e-mail: dev-unsubscr...@openoffice.org
For additional commands, e-mail: dev-h...@openoffice.org

Reply via email to