Hi Mattias,
May I suggest you make the app return -1 on
failure, or even better number of errors. That way your app is very
easy to configure as a testcase to be run by ctest.
Done.
or better:
ADD_TEST("Plugin tiff reader" osgpluginstest --imageReaders tiff)
ADD_TEST("Plugin png reader" osgpluginstest --imageReaders png)
...
To get test results per plugin
The latter could be put in each plugin's CMakeLists.txt under src/osgPlugins/xxx
Hehehe... That's really clever. Though that would only test a plugin in
isolation (reading its own format, writing what was read to its own
format). One interesting thing about the test I did is that it tests
each reader in combination with each writer. I have actually found some
weird incompatibilities (DDS images can't be written back as png or tiff
for example, I haven't investigated why...) using this mechanism. This
might reveal bugs beyond whether a plugin reads or writes files.
With that schema we could get tests run by all sites building and
reporting to our Dashboard. If you want I can help with the cmake
stuff once you get the app into svn.
Yep, that would be very nice. Thanks for the offer, we'll see where we
go with this.
One next step I'd like is to test the geometry/model readers/writers
too. Perhaps just testing reading a model in a given format, and then
writing that same model to the same format would give a first level of
testing, and then perhaps comparing the input and output files would
give a second level, though that might not even be expected to work for
most plugins...
Thanks for your comments.
J-S
--
______________________________________________________
Jean-Sebastien Guay [email protected]
http://www.cm-labs.com/
http://whitestar02.webhop.org/
_______________________________________________
osg-submissions mailing list
[email protected]
http://lists.openscenegraph.org/listinfo.cgi/osg-submissions-openscenegraph.org
