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

[Rafael Laboissiere]

* John W. Eaton <jwe at bevo.che.wisc.edu> [2008-03-19 17:30]:

> The "%!test" line is not necessary, so you might find more files if
> you also searched for "%!assert".

Thanks for the reminder, John.

I just added check.m for octave-signal.  The file was generated using the
following command, after the package was built (sorry, Thomas, it uses Perl
:-)

    $ find debian/ -name \*.m \
      | xargs grep -l '^%!\(assert\|test\)' \
      | perl -pe 's:.*/(.*)\.m::; print "disp (\"[$1]\")\ntest $1"' \
      > debian/check.m

and the result is:

    $ cat debian/check.m
    disp ("[filtic]")
    test filtic
    disp ("[sgolay]")
    test sgolay
    disp ("[specgram]")
    test specgram
    disp ("[upsample]")
    test upsample
    disp ("[rectpuls]")
    test rectpuls
    disp ("[sos2zp]")
    test sos2zp
    disp ("[tripuls]")
    test tripuls
    disp ("[residued]")
    test residued
    disp ("[pulstran]")
    test pulstran
    disp ("[downsample]")
    test downsample
    disp ("[zp2sos]")
    test zp2sos
    disp ("[residuez]")
    test residuez
    disp ("[triang]")
    test triang
    disp ("[idst]")
    test idst
    disp ("[convmtx]")
    test convmtx
    disp ("[dst]")
    test dst
    disp ("[grpdelay]")
    test grpdelay
    disp ("[cplxreal]")
    test cplxreal
    disp ("[rceps]")
    test rceps
    disp ("[sos2tf]")
    test sos2tf
    disp ("[czt]")
    test czt
    disp ("[tf2sos]")
    test tf2sos
    disp ("[fir1]")
    test fir1

Now, I am wondering whether the tests could be done automatically by piping
the output of the command above into Octave instead of sourcing the
debian/check.m file.  I could implement this in octave-pkg-dev.  We can
still keep debian/check.m for extra tests that are not included in the
sources.

What do you think?

-- 
Rafael