BIST for m-files: Difference between revisions

→‎Overview: update description based on current list of missing tests
(→‎Functions lacking tests (as of May 27, 2015): updated list from current fntests.log)
(→‎Overview: update description based on current list of missing tests)
Line 3: Line 3:
These m-files do not have built-in tests.
These m-files do not have built-in tests.


Sometimes this is because the function is interactive, like the @ftp class, and would be very difficult to test.
Sometimes this is because the function is interactive, like the inputdlg function, or reads data from a device like the @audiorecorder class, and would be very difficult to test.


Sometimes this is because the output is graphical, such as the plot routines, and would be difficult to test without image comparison routines.  These functions often have %!demo blocks instead.
Sometimes this is because the output is graphical, such as the plot routines, and would be difficult to test without image comparison routines.  These functions often have %!demo blocks instead.
296

edits