[Paraview-developers] Testing external plugins

David Thompson david.thompson at kitware.com
Fri Aug 3 16:22:40 EDT 2012


Hi Utkarsh,

> We don't really have a good support to add tests totally externally
> (out of paraview's source dir).
> ...

OK, I guess until that changes either we run the tests manually or configure dashboard machines very carefully. :-)

>> + How should ParaView be invoked? It doesn't look like ParaViewConfig.cmake specifies the location of the ParaView executable. It does record the paths to pvbatch, pvpython, and all the server executables, but not the GUI... and that apparently needs to be provided to smTestDriver via "--client". For that matter, it doesn't look like ParaViewConfig.cmake is installed anywhere.
> 
> This will be much easier following the changes that coming to ParaView
> soon (ParaView Modularization). paraview, pvserver etc are targets
> exported from ParaView and hence external project can add test by
> simply referring to the target name in add_test(NAME.. COMMAND ..)
> calls.

Excellent!

	Thanks,
	David


More information about the Paraview-developers mailing list