1.3.0
Release overview
- Easy configuration of alternative AMD loaders
- Easier command-line usage
- More code coverage analysis and reporting
- Improvements and bug fixes to suite
beforeEach
/afterEach
methods - More reliable WebDriver connections
- Grunt events
- Many other bug fixes
Important, backwards-incompatible changes
- The
beforeEach
andafterEach
methods of all nested parent suites are now called before and after each test. Previously, only thebeforeEach
andafterEach
methods of the nearest parent of the test would execute. (#67) - The way in which module paths are resolved has changed. Previously, paths were always relative to two directories above the Intern directory. Now, on the command-line, paths are relative to the current working directory. As part of this change, the
baseUrl
loader option can now be set to any arbitrary path, and Intern should be able to be installed to any location without any directory structure restrictions. (#89) - Configuration files can no longer be loaded from a cross-origin source in order to prevent XSS attacks on public installations of Intern. (87764c6)
Enhancements
- The AMD loader used by
intern-client
is now configurable from within the Intern configuration file. This enables the use of alternative loaders like RequireJS without making any modifications to files that come with Intern. (#90) - Unit tests executed in Node.js with
intern-client
are now instrumented for code coverage analysis and reporting. (#5) - Grunt events are now fired when each test passes and fails. (#73)
- Path resolution logic has been overhauled to be more robust. (#89)
- New
intern-client
andintern-runner
commands have been added so you do not need to runnode
directly. (#89) - Per-file code coverage information is now displayed by the console reporter. (#96)
- Unhandled exception error reporting in HTML5 Living Standard browsers is now improved. (c03cbc0)
- The
wd
dependency has been updated to 0.2.2, which includes support for Sauce Labs API calls. (#97)
Bug fixes
- Robustness enhancements have been added to Sauce Connect connections to avoid test hangs due to tunnel collisions. (#4, #82)
- The total number of tests are now calculated correctly in the test runner. (#86)
- Bogus error messages generated when Sauce Connect is closed are now suppressed. (bermi/sauce-connect-launcher#12)
- Calling
remote.isEnabled()
will no longer hang the test runner. (#75) - The
stop
method of a reporter is now actually called when all tests have finished executing. (#74) executeAsync
can now be passed functions. (#92)- Generated
lcov.info
files now use full paths to conform to the lcov spec. (#95) - Returning promises from a functional test’s
remote.then
callback will now cause the runner to wait until the promise is resolved before executing the next command. (#93) - Running tests against a pre-existing Sauce Connect tunnel (
useSauceConnect: false
) will now work if notunnel-identifier
is explicitly provided. (1c47182) - Non-spec-compliant zlib compression of responses has been removed. (8943bf4)
Install from npm
Regular edition
|
or |
Geezer edition
|