Release Notes - Unitils - Version 3.0 - HTML format

Bug

[UNI-124] - PartialMock objects not properly constructed
[UNI-130] - When you try to make a void method return a value when mocking, the stacktrace is not correct
[UNI-150] - If a method returns a primitive value, the logged scenario indicates that "null" is returned
[UNI-166] - Typo in 2nd paragraph of web home page - asserion
[UNI-168] - Mocks to not behave correctly when they are cast to a parent of the class they mock.
[UNI-169] - PartialMock objects still not properly constructed
[UNI-174] - Disabling constraints doesn't work

Improvement

[UNI-158] - Use names of test class instance fields in scenario reports
[UNI-159] - Add ability to specify default behavior for mocks. (find best match for invocations)
[UNI-170] - Use reg expression to harvest the number for indexing scripts.

New Feature

[UNI-115] - Split unitils into multipe distributables: 'unitils-core' and a number of module jars
[UNI-153] - Support defining behavior and assertions using chained methods, e.g. mock.returns(value).getSomething().getValue();

Edit/Copy Release Notes

The text area below allows the project release notes to be edited and copied to another document.

Release Notes - Unitils - Version 3.0
    
<h2>        Bug
</h2>
<ul>
<li>[<a href='http://jira.unitils.org/browse/UNI-124'>UNI-124</a>] -         PartialMock objects not properly constructed
</li>
<li>[<a href='http://jira.unitils.org/browse/UNI-130'>UNI-130</a>] -         When you try to make a void method return a value when mocking, the stacktrace is not correct
</li>
<li>[<a href='http://jira.unitils.org/browse/UNI-150'>UNI-150</a>] -         If a method returns a primitive value, the logged scenario indicates that &quot;null&quot; is returned
</li>
<li>[<a href='http://jira.unitils.org/browse/UNI-166'>UNI-166</a>] -         Typo in 2nd paragraph of web home page - asserion
</li>
<li>[<a href='http://jira.unitils.org/browse/UNI-168'>UNI-168</a>] -         Mocks to not behave correctly when they are cast to a parent of the class they mock.
</li>
<li>[<a href='http://jira.unitils.org/browse/UNI-169'>UNI-169</a>] -         PartialMock objects still not properly constructed
</li>
<li>[<a href='http://jira.unitils.org/browse/UNI-174'>UNI-174</a>] -         Disabling constraints doesn't work
</li>
</ul>
    
<h2>        Improvement
</h2>
<ul>
<li>[<a href='http://jira.unitils.org/browse/UNI-158'>UNI-158</a>] -         Use names of test class instance fields in scenario reports
</li>
<li>[<a href='http://jira.unitils.org/browse/UNI-159'>UNI-159</a>] -         Add ability to specify default behavior for mocks. (find best match for invocations)
</li>
<li>[<a href='http://jira.unitils.org/browse/UNI-170'>UNI-170</a>] -         Use reg expression to harvest the number for indexing scripts.
</li>
</ul>
    
<h2>        New Feature
</h2>
<ul>
<li>[<a href='http://jira.unitils.org/browse/UNI-115'>UNI-115</a>] -         Split unitils into multipe distributables: 'unitils-core' and a number of module jars
</li>
<li>[<a href='http://jira.unitils.org/browse/UNI-153'>UNI-153</a>] -         Support defining behavior and assertions using chained methods, e.g. mock.returns(value).getSomething().getValue(); 
</li>
</ul>