On 03/13/2012 10:57 PM, Luca Favatella wrote: [...] > Hello, > > What input/output arguments do you propose for the runUnitTests.m file? > Shouldn't that file have the package name in its name in order to > avoid name clashes, e.g. mypackage_runUnitTests.m ? > > I am interested in the best practices for exposing the unit test suite > as I am currently polishing the ga package [0]. > The control package defines a test_control.m [1] script (without > output arguments) in order to run all unit tests.
Hi, I am very much interested as well. In the queueing package I use a brutally hacked version of the fntests.m script from Octave to extract and run all tests from all script files. I use a makefile target to do this using "make check", but I would appreciate a more user-friendly, "pure" Octave solution. A feature I really like about Octave's fntests.m is that I get a nicely formatted output telling, for each file, how many tests have been run and how many of them failed. If there are suggestions of better ways to do this, I am willing to follow them. Moreno. -- Moreno Marzolla EMail: mor...@moreno.marzolla.name WWW : http://www.moreno.marzolla.name/ ------------------------------------------------------------------------------ Virtualization & Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ _______________________________________________ Octave-dev mailing list Octave-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/octave-dev
