<li>Jasmine no longer logs “Jasmine Running…” messages to the log by default. This can be enabled in runner.html by adding ’ trivialReporter.logRunningSpecs = true;’</li>
<li>The ‘wasCalled’, ‘wasCalledWith’, ‘wasNotCalled’ and ‘wasNotCalledWith’ matchers have been deprecated. The new matchers ‘toHaveBeenCalled’ and #‘oHaveBeenCalledWith’ have been added. You can use the ‘not’ method to achieve the ‘wasNot…’ expectation. (e.g. ‘not.toHaveBeenCalled’)</li>
</ul>
<h4>Notables</h4>
<ul>
<li>A barebones version of Jasmine is now available on http://pivotal.github.com/jasmine</li>
</ul>
<h2>Release 0.11.0 — June 23, 2010</h2>
<h3>Jasmine Core</h3>
<h4>Features</h4>
<ul>
<li>The version number has been removed from the generated single-file /lib/jasmine.js. We’re also now uploading this file, with the version number in the filename, to github’s Downloads page.</li>
<li>Old-style matchers (those using this.report(), from before 0.10.x) are no longer supported. See the <spanclass="caps">README</span> for instructions on writing new-style matchers.</li>
<li><strong>jasmine.log</strong> pretty-prints its parameters to the spec’s output.</li>
<li>Jasmine no longer depends on ‘window’.</li>
<li><spanclass="caps">HTML</span> runner should show number of passes/fails by spec, not expectation.</li>
<li>Small modification to JsApiReporter data format</li>
</ul>
<h4>Bugs fixed:</h4>
<ul>
<li>If multiple beforeEach blocks were declared, they were executed in reverse order.</li>
<li>Specs with duplicate names confused TrivialReporter output.</li>
<li>Errors in describe functions caused later tests to be weirdly nested.</li>
<li>Nested specs weren’t reported properly by the JsApiReporter.</li>
</ul>
<h4>Known issues:</h4>
<ul>
<li>If you turn on the mock clock, you’ll get a spurious log message at the end of your spec.</li>
