On 13 Mar 2012, at 22:22, Thomas Weber wrote: > On Tue, Mar 13, 2012 at 09:04:42PM +0100, c. wrote: >> Actually there is no simple way to automatically run all tests in a package, >> it would be nice to have a command like >> >> pkg test <package_name> >> >> or rather >> >> pkg install -test <package_name> >> >> as the source code must be availableto run tests in .cc files. > > That's only an issue if you insist that tests must stay in .cc files. > While this makes sense for Octave, it might make more sense for > octave-forge packages to just ship a runUnitTests.m file with all tests > in just one file. Easier to explain to newcomers and easier to implement > in pkg.m. Or, create a test/ directory and all .m files therein are > considered test code.
or test blocks in .cc files could be automatically extracted and saved in the tests/ directory upon installation as is currently done for //PKG_ADD / //PKG_DEL directives. Any of the options above seems cool to me, unfortunately I don't have time to implement them at the moment :( > Thomas c. ------------------------------------------------------------------------------ Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d _______________________________________________ Octave-dev mailing list Octave-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/octave-dev
