2.2.0
Release overview
♨️ Check out the highlights on our blog!
- New pretty reporter
- New actual/expected object difference output
- Enhanced error detection and reporting during startup
- Updated to Dig Dug 1.2
- Bug fixes
Special thanks to @devpaul, @jason0x43, @neonstalwart, @unrealguard, and @vladikoff for their code contributions!
Additional thanks to @Blasz and @zanona for submitting tickets that were addressed in this release!
Enhancements
- A new pretty reporter that displays progress bars for each environment during test runs has been added. This new reporter will become the default reporter for the Node.js client and the test runner in a future release. For now, try it by setting
reporters=pretty
on the command-line. (#258) - When an assertion error occurs because an actual object doesn’t match the expected object, the logged error message will now show a unified diff between the two objects. Undefined properties, regular expressions, dates, arrays with properties, functions with properties, etc. are all supported. (7c051e9)
- Improved error handling so early errors in test modules (like syntax errors) are now correctly caught and reported by the test system. (#254)
- On Geezer,
assert.deepEqual
should now work the same as Chai’sdeepEqual
when comparing typed objects. (#284) - Additional enhancements in Dig Dug 1.2
Bug fixes
- Fixed an issue where source maps referenced with relative paths would sometimes not be discovered by the source mapping system. (#303)
- Fixed a rare condition where Intern installation would fail in cases where npm deduped all of Intern’s dependencies and deleted its
node_modules
directory. (#302) - Fixed a problem where the HTML reporter wouldn’t recognise tests as skipped if their skip message was empty. (#295)
- Fixed a problem with the TeamCity reporter where the reporter used ISO-8601–compliant date strings, but TeamCity doesn’t fully comply with ISO-8601. (#287)
- Additional bug fixes in Dig Dug 1.2
Install from npm
Regular edition
|
or |
Geezer edition
|