296
edits
Projects: Difference between revisions
Jump to navigation
Jump to search
→Tests: encourage use of make check to run tests, __run_test_suite__ if not building from source
Carandraug (talk | contribs) (→Input/Output: suggest xmlread and xmlwrite based on Xerces) |
(→Tests: encourage use of make check to run tests, __run_test_suite__ if not building from source) |
||
| Line 261: | Line 261: | ||
We are far from even having one test for every function, so focus should be on getting the breadth of coverage first before trying to get the depth of 100% statement coverage. As of Jan 2014, 243 of 834 m-files have no tests. Some of these will be plotting functions which have demos instead, but that leaves enough functions to be an interesting project. | We are far from even having one test for every function, so focus should be on getting the breadth of coverage first before trying to get the depth of 100% statement coverage. As of Jan 2014, 243 of 834 m-files have no tests. Some of these will be plotting functions which have demos instead, but that leaves enough functions to be an interesting project. | ||
After Octave is compiled, running the {{Codeline|make check}} build target will run the full test suite and generate a file called test/fntests.log in the build directory with a summary of the results. At the end of the file is a list of all functions for which no tests were found. An extract is posted in the [[files missing tests]] page. If you are not building Octave yourself, the test suite can be run on an installed binary copy by executing the {{Codeline|__run_test_suite__}} command at the Octave prompt. The fntests.log file will be written in the current directory in this case. | |||
fntests.log in | |||
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 | ||