On Thu, Jun 12, 2008 at 2:36 PM, Luc Bollen <> wrote:
On Thu, Jun 12, 2008 at 1:49 PM, Peter Dolding <> wrote:
For evaluation of what software is going to be used by a company to
create ODF documents simple testing of the application is also needed.
Acid Test is well suited to validate the Input part of the application ("Does the application correctly handle valid ODF files?"): simply open the standard Acid Test file, and see how it is displayed by the application.
However, it is not well suited to validate the Output part of the application ("Does the application produce valid ODF files?").
I have just been thinking about the different ways to do an Acid Test - for browsers it's just a URL but for documents it's more difficult. One can either make documents available for users to load into the subject (where they could be observed, screenshotted(?) or saved to PDF) or one can upload documents the subject produces for online analysis... or both. The beauty of the latter is that once you have simple uploader framework the tests are easily augmented by the 'prodders' (who would hopefully be prodding useful rather than esoteric functionality first).
There are some simple & dirty tests I have already concieved that could potentially give some interesting results... like extension to in-spec ratio (%), or running a diff over before & after docs that have been simply opened and saved.
There is clearly a /lot/ of interest here...
Sam
