1.2.0
Release overview
- Better support for alternative AMD loaders
- Improvements and bug fixes to functional testing
- More API compatibility across normal and geezer versions
- Easier access to geezer edition from npm
Important, backwards-incompatible changes
- The geezer edition of Intern now uses the npm package name
intern-geezerinstead ofinterndue to restrictions in the way npm versioning works. This means it will install tonode_modules/intern-geezerinstead ofnode_modules/intern. Tests themselves are unaffected because the AMD package still registers using the nameintern(yay AMD!).
Enhancements
- Initial inline documentation on PromisedWebDriver has been added. Documentation will continue to be improved in the next release. (#58)
- The Node.js client and the test runner have been updated so that they close servers and exit gracefully instead of forcibly quitting the Node.js process at the end of the test run. This enables custom reporters to perform asynchronous operations that may not complete by the time tests are finished executing (like sending test results to a remote server). This also fixes some bugs where Intern would not output all test results if executed as a child process (e.g. with Grunt). (#68)
- Intern no longer has any dependency on Git for installation.
- The default example configuration now enables testing of Firefox versions 20+ by updating the Selenium version to 2.33.0.
- The value of the
configcommand-line option is now passed as the name of the session to Sauce Labs so that it displays something more meaningful than “unnamed job” by default. (#41) - Required proxy, webdriver, and idle timeout configuration options are now defaulted within the test runner. This enables configuration files to be smaller, if desired. (#32, #60)
- (geezer) An
intern/chaiplugin module has been added to provide API parity for tests that use assert-style assertions. (#70) - (geezer) Geezer is now published as a separate npm package in order to be easier to install. Simply use the package name
intern-geezerinstead ofinternwhen installing.
Bug fixes
- The has.js implementation from the underlying Dojo 2 code has been updated so that alternative AMD loaders (like RequireJS) can be successfully used by clients. Just replace
dojo.jswith your preferred AMD loader inclient.html. (#59) - When a functional test fails, subsequent tests no longer also fail. (#46, #69)
- Nesting calls to a remote environment from within a
thencallback no longer deadlocks. (#14) consolereporter self-tests no longer incorrectly close groups. (#66)- PromisedWebDriver methods that should call Element methods directly instead of passing an Element to a method no longer crash. Notably, this means that
clickcan now be used instead ofclickElement, and nestedelementBy*calls now work as intended. (#52) webdriverreporter no longer generates invalid DOM structures. (#65)- Long-running unit test suites will no longer cause Selenium/Sauce Labs to time out and close the remote browser due to inactivity in the WebDriver control channel. (#49, #61)
Install from npm
Regular edition
|
or |
Geezer edition
|