Back to the subject at hand...
I haven't explored it before, but cmake also has the ability to perform
automated unit testing through ctest. I've already created a cmake config
to build all the executables in the unittest directory but I'm not
currently doing anything with them.
If someone would explain how some of these work (and would want an easy way
to automate testing) I'll need some info:
which test (executable)
What does the command line look like to run the test?
How are the results evaluated?
For instance, octave did a good job a graphically showing the difference
between two versions of libcodec2, but is there an arithmetic equivalent
which produces a value such as you would get from standard curve fits?
I.e., perfect is 1, any deviation causes a result <1 where we can set a
threshold?
Thanks,
Richard
------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:
Build for Windows Store.
http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
Freetel-codec2 mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/freetel-codec2
