2

Closed

update unit tests

description

The units were started in 2003 and unit testing "techniques" and best practices have changed since then. We need to update and simplify the tests. Redo the unit tests so they can be used as documentation/specifications. Create a separate test project for testing numerical accuracy. Use FsCheck or Pex to do corner case and random value testing.
Closed Sep 7, 2009 at 10:49 AM by cuda
Redoing in MathNet.Numerics

comments

jvangael wrote May 25, 2009 at 10:49 AM

I think we should start as soon as we can on this as we might have to do write unit tests twice (in old system now and redo them in new system in a few weeks/months time). I have no experience with more recent unit testing methods but am happy to learn and use them. One request though: I think we should also have a project where we can test the correctness of sampling methods: the only way I can think of doing this is generating 1000's of samples and checking that the moments (mean,variance) are within certain bounds. These tests would very likely take much longer to run than the current unit tests.

pvandervelde wrote May 25, 2009 at 9:51 PM

I was planning to create a little application to do verification testing of the iterative solvers. The plan was to find a bunch of test matrices and run the solvers on those. Afterwards we compare the results with the known good results. I guess if we approach it the right way then we can create a general verification tool which would work for the testing of the sampling methods too.

wrote Sep 7, 2009 at 10:49 AM

wrote Feb 14, 2013 at 3:00 AM

wrote May 16, 2013 at 8:16 AM