1.5.0
Release overview
- Improved support for mocking AMD dependencies
- Out-of-the-box PhantomJS support
- Improved remote debugging for test failures
- Bug fixes
Enhancements
- The de-facto standard
require.undef
function has been added to the Dojo 2 loader, making it possible to mock AMD dependencies from test modules using Intern’s default loader by undefining, mapping, and reloading dependencies. Additional improvements to simplify this process will be introduced in the future, but it is now at least possible to do it. (#47) - The standard version of Intern will now run inside a PhantomJS environment. However, please exercise caution here; if you don’t know the reasons why you shouldn’t use PhantomJS, you probably should not use PhantomJS. (#154)
- A new
leaveRemoteOpen
command-line flag has been added. When specified, Intern won’t quit the test browser after tests have completed, so you can use it to manually inspect your browser state post-test. (#144)
Bug fixes
- Testing will no longer break when
intern-runner
is executed from a different child directory than the configuredbaseUrl
directory. (#139) client.js
will no longer fail when using alternative AMD loaders without settingNODE_PATH
in the standard version of Intern. Node.js modules loaded withintern/dojo/node
will also now use the same path resolution mechanism as real Node.js modules. Equivalent functionality will be introduced to the geezer version of Intern in a future release. (#147)- The Grunt task no longer incorrectly assumes that output from the test runner is received one line at a time. This caused additional incorrect reporting and highlighting of pass/fail messages. (#152)
- Using promises without
cancel
methods will no longer cause failures of the test system when their associated tests time out. (#151)
Install from npm
Regular edition
|
or |
Geezer edition
|