[Pkg-octave-devel] check.m for the forge packages

[Rafael Laboissiere]

* Ólafur Jens Sigurðsson <ojsbug at gmail.com> [2008-03-20 18:11]:

> On Thu, Mar 20, 2008 at 04:35:22PM +0100, Rafael Laboissiere wrote:
> > * Ólafur Jens Sigurðsson <ojsbug at gmail.com> [2008-03-20 00:31]:
> > 
> > > The implementation in octave-pkg-dev sounds nice. But I am just not
> > > getting the point of all this. Is this really neccesery?
> > 
> > Nearly all packages maintained by the DOG run tests.  This is also typically
> > the case in Debian as general.  Running tests at package build is of great
> > help to detect problems before uploading or even on the autobuilders.
> 
> Yes, that's what I thought but looking at the source that does call
> the test routine there is no checking if the test succeeded, so this
> is just a visual for the user and has nothing to do with automation?

Yes, it is visual and the package build is not aborted when the check fails.
n I build the octave-signal with the latest (0.3) octave-pkg-dev, I see:

Checking package...
[filtic]
PASSES 6 out of 6 tests
[...]
[residued]
  ***** test
 B=1; A=[1 -1];
 [r,p,f,m] = residued(B,A);
 assert({r,p,f,m},{1,1,[],1},100*eps);
 [r2,p2,f2,m2] = residuez(B,A);
 assert({r,p,f,m},{r2,p2,f2,m2},100*eps);
!!!!! test failed
error: invalid vector index = 2
 
> If that is the case, then I can do some other tests that are not based
> on the test function in octave for those packages that don't have that
> implemented.

With you are willing to do it, it is great, go ahead.

-- 
Rafael