Projects: Difference between revisions

Jump to navigation Jump to search
122 bytes removed ,  10 January 2014
m
→‎Tests: harmonizing edits
m (Add link to FilesMissingTests)
m (→‎Tests: harmonizing edits)
Line 245: Line 245:
=Tests=
=Tests=
*Improved set of tests:
*Improved set of tests:
**Tests for various functions. Would be nice to have a test file corresponding to every function.
**Tests for various functions. Would be nice to have a test file corresponding to every function (see below)
See [[FilesMissingTests]] for a list of m-files without tests.  Many of the plotting functions have demos rather than tests and this is acceptable.
**Tests for element by element operators: + - .* ./ .\ .^ | & < <= == >= > != !
**Tests for element by element operators: + - .* ./ .\ .^ | & < <= == >= > != !
**Tests for boolean operators: && ||
**Tests for boolean operators: && ||
Line 260: Line 259:


On release 3.8.x, executing the __run_test_suite__ function will generate a file called  
On release 3.8.x, executing the __run_test_suite__ function will generate a file called  
fntests.log in your current directory with a summary of the results.  It indicate at the end the functions for which no tests were found in file.  An extract is posted in [[Missing tests]].
fntests.log in your current directory with a summary of the results.  It indicate at the end the functions for which no tests were found in file.  An extract is posted in the [[files missing tests]] page.


There also need to be tests for functions written in the C++ files, and that is a  
There also need to be tests for functions written in the C++ files, and that is a  
115

edits

Navigation menu