mlUnit

File Release Notes and Changelog

Release Name: 1.5.1

Notes:
For a nicely formatted release notes page, see <http://mlunit.dohmke.de/Release/1.5.1>.

Changes:
New Features:

(1) assert is a built-in function of MATLAB R2007a

With the new release of MATLAB, R2007a, assert became a built-in function. Therefore the following warning appears, when adding the directory src to the MATLAB path:
  Warning: Function src\assert.m has the same name as a 
  MATLAB builtin. We suggest you rename the function to 
  avoid a potential name conflict.
To avoid this warning, release 1.5.1 brings a new method for the installation of mlUnit: 

1. Unzip mlunit_1.5.1.zip to $HOME.
2. Change to directory in MATLAB:
>> cd $HOME/mlunit/src
3. Run install method:
>> install(mlunit);
4. Add directory to MATLAB path:
>> addpath('$HOME/mlunit/src');

For R2007a the method assert.m will be renamed to mlunit_assert.m, for older releases it will remain without any changes. Please note that it is recommended to continue to use assert within tests (and not to rewrite the tests due to the change from assert to mlunit_assert), as the built-in assert and the assert of mlUnit are compatible to each other. Therefore, all of the following statements within a test case cause a red bar:

assert(false);
mlunit_assert(false);
fail();

********************************************************************************

Fixed Bugs:

(1) Formatting of error messages

The error message within the GUI was not usable for the some test cases, see 
<http://sourceforge.net/tracker/index.php?func=detail&aid=1641927&group_id=166995&atid=841178>

(2) Method gui_test_runner/shorten_error_text

The method shorten_error_text appended the last part of a first path of a stacktrace to the next path of the same stacktrace, if the latter one is shorter than the first one. The reason is that a cell string was not initialized. See
<http://sourceforge.net/tracker/index.php?func=detail&aid=1643880&group_id=166995&atid=841178>

(3) Method test_result/add_error_with_stack

The method add_error_with_stack used dbstack and therefore did not include the file, where the error really happened. See
<http://sourceforge.net/tracker/index.php?func=detail&aid=1645658&group_id=166995&atid=841178>