Projects: Difference between revisions

267 bytes added ,  28 March 2014
→‎Tests: Add coverage tool project idea
(→‎Tests: encourage use of make check to run tests, __run_test_suite__ if not building from source)
(→‎Tests: Add coverage tool project idea)
Line 258: Line 258:
***assignment of empty matrix as well as values resizing
***assignment of empty matrix as well as values resizing
**Tests for all internal functions.
**Tests for all internal functions.
* Implement a coverage tool for collecting coverage data and generating code coverage reports on m-file functions and scripts. This would be very useful for Octave development as well as for users who want a code coverage report for their own functions and scripts.


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.
296

edits