jasmine/release-notes.html.markdown

2.3 KiB
Raw Blame History

layout title
default Jasmine Release Notes

Release Notes

Release 0.11.1 — June 25, 2010

Jasmine Core

Features

  • Jasmine no longer logs “Jasmine Running…” messages to the log by default. This can be enabled in runner.html by adding trivialReporter.logRunningSpecs = true;
  • 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)

Notables

Release 0.11.0 — June 23, 2010

Jasmine Core

Features

  • The version number has been removed from the generated single-file /lib/jasmine.js. Were also now uploading this file, with the version number in the filename, to githubs Downloads page.
  • Old-style matchers (those using this.report(), from before 0.10.x) are no longer supported. See the README for instructions on writing new-style matchers.
  • jasmine.log pretty-prints its parameters to the specs output.
  • Jasmine no longer depends on window.
  • HTML runner should show number of passes/fails by spec, not expectation.
  • Small modification to JsApiReporter data format

Bugs fixed:

  • If multiple beforeEach blocks were declared, they were executed in reverse order.
  • Specs with duplicate names confused TrivialReporter output.
  • Errors in describe functions caused later tests to be weirdly nested.
  • Nested specs werent reported properly by the JsApiReporter.

Known issues:

  • If you turn on the mock clock, youll get a spurious log message at the end of your spec.