Hi Frank,
Frank Schönheit - Sun Microsystems Germany pisze:
Hi Marcin,
Heh, if that IDE would somehow fit with JUnit, then even non-core
developers could start contributing tests... But I'm pretty pessimistic
about it
OOo has built-in support for "scripting" its UI via testtool. That is,
connects to a running OOo on a dedicated port, and sends commands for
simulating UI events. (Well, this is most probably a somewhat simplified
description, actually, I know too little about testtool.)
Yes, I roughly know how testtool works as I had to correct some Basic
code in it to make it work (it was a long time ago).
So, I somehow believe that replacing testtool with, simplified again,
some Java classes, which implement the communication protocol, would
give us a possibility for much more rapid UI test development.
Replacing Basic with Java would already be a great step ahead. It's a
pain to debug Basic code.
But if you're talking about ideal solutions, then the ideal solution
would be to have the UI elements defined with some XML, with some
internal testing parameters inherent in the XML (like permissible output
values or something like this). A GUI IDE for this XML development would
be used for prototyping the UI, and then you would just check if the
resultant UI works as expected in the spec. Note: I'm not thinking about
XML used for config files in OOo, where you cannot do any reasonable
validation and expect this to work, I'm thinking about much stricter
XML, maybe something like XUL (on steroids, possibly).
But somehow I don't believe it could become reality any time soon. Too
much code is already there.
Regards
Marcin
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
