Merge pull request #1954 from joeycozza/master
Update debug dependency to 2.2.0
Update debug dependency to 2.2.0
debug@2.0.0 has a vulnerability in its dependency on ms@0.6.2.
debug@2.2.0 has updated its ms dependency to a version without this vulnerability.
Merge pull request #1910 from nexdrew/fix/mocha-opts-dupe
Fix duplication of mocha.opts on process.argv
remove duplication of mocha.opts on process.argv
Merge pull request #1909 from berkerpeksag/patch-1
Fix typo in test/reporters/nyan.js
Fix typo in test/reporters/nyan.js
peinding -> pending
Merge pull request #1889 from danielstjules/issue-1798
Fix #1798: Correctly attribute mutiple done err with hooks
Fix #1798: Correctly attribute mutiple done err with hooks
Merge pull request #1880 from danielstjules/stackfilter-browser
Stackfilter fix: Don't remove modules/components from stack trace in the browser
Merge pull request #1888 from danielstjules/revert-jade
Revert jade to support npm < v1.3.7
Merge pull request #1886 from danielstjules/uncaught-delay
Fix #1669: catch uncaught errors outside test suite execution
Remove redundant harmony flag
Cast non-string return values from err.inspect()
Call the inspect() function if message is not set
Unfortunately some frameworks throw error objects which do not have a message
property but do have an inspect() function. This means Mocha reports a test
failure, but prints the empty string instead of any useful information about
the error message. For an example, see versions of the Waterline ORM before
v0.10.19: https://github.com/balderdashy/waterline/commit/0965d132
If the message key is not set on an error object, attempt to print the same
output as console.log in Node, by calling the object's inspect() function,
if it exists.
We could try to fallback to calling util.inspect on the err object and
logging that, but I'm not sure the format would be appropriate.
Revert jade to support npm < v1.3.7
Fix eqeqeq linting errors from eslint 1.4.0 release
Fix #1669: catch uncaught errors outside test suite execution
fix package.json to use exact version of lodash; closes #1867
Merge pull request #1852 from aaroncrows/fix/1812-bail-runs-before-hooks
Fix: Bail flag causes before() hooks to be run even after a failure
Fix: Bail flag causes before() hooks to be run even after a failure
2.3.0 / 2015-08-31
Release v2.3.0
update HISTORY.md for v2.3.0
rebuild mocha.js
added allowUncaught option (#553)
allows unhandled exceptions to propagate in the browser
added tests for allowUncaught option
global error handler prints to dom with allowUncaught
Allow --async-only to be satisfied by returning a promise
This results in a slight change to the behavior of --async-only:
instead of failing immediately, check to see if the test returned
a promise (or otherwise failed) before complaining about not
having a done callback.
upgrade eslint to 1.2.1 w/ config & Makefile fixes
Merge pull request #1829 from gigadude/gigadude-max-old-space-size
Support --max-old-space-size node argument
Merge pull request #1835 from outsideris/issue-1811
Upgrade Jade dependency to 1.11.0
upgrade jade to v1.11.0
Jade syntax isn't broken in new version, but update some syntax
for being more explicitly. fix #1811
fix undefined str variable for html coverage
Order for variables definition is wrong in 3f78f10ca,
so, html coverage page print <undefined></undefined>
because str is undefined in jade.compile(str, { filename: file });.
Support --max-old-space-size node argument
Merge pull request #1802 from ajaykodali/fix/1769-asynchronous-error-handling
Fix for async hook error handling issue
* Fixed async hook error handling issue where an error in the hook was bailing sibling suites too
Added unit test cases for async hook error handling
Fixed minor issue in existing sync hook error test case
Moving code to fixtures dir to make the hook.err.js tests more readable
Trimming the hook error test cases by removing hooks not under test
Fix indentation
Rename var to afterAllHookCalled
Merge pull request #1447 from duncanbeevers/descriptive-before-after-each
Decorate failed hook titles with test title
Scope loading behaviour instead of using early return
Fails under babel_node node_modules/mocha/bin/_mocha
Transformation error; return original code
{ [SyntaxError: node_modules/mocha/bin/_mocha: 'return' outside of function (392:2)]
pos: 9902,
loc: { line: 392, column: 2 },
raisedAt: 9908,
_babel: true,
codeFrame: ' 390 | });\n 391 | \n> 392 | return;\n | ^\n 393 | }\n 394 | \n 395 | // load' }
based on advice from @oakfang
Signed-off-by: Joshua Appelman jappelman@xebia.com
Closes #1787
Merge pull request #1788 from sunesimonsen/fix/html-runner
Fix: html-runner crashing because of missing process.stdout shim
Fix: html-runner crashing because of missing process.stdout shim
When running mocha in the browser you get a crash in the following code:
if (isatty) {
exports.window.width = process.stdout.getWindowSize
? process.stdout.getWindowSize(1)[0]
: tty.getWindowSize()[1];
}
That is because we need to shim the process.stdout before requiring
mocha from browser-entry.js, I fixed that by moving it to the top of the
file.
Merge pull request #1749 from tinganho/maxiumCErr
Maximum call stack issue for large test suite
Fixes maximum call stack error
Merge pull request #1784 from ndhoule/refactor/remove-browserify-todo
Remove TODO from Browserify transition
Remove TODO from Browserify transition
Decorate failed hook titles with test title
Fixes #1230
2.3.4 / 2015-11-15
2.3.3 / 2015-09-21
messageproperty but do have aninspect()function. This means Mocha reports a test failure, but prints the empty string instead of any useful information about the error message. For an example, see versions of the Waterline ORM before v0.10.19: https://github.com/balderdashy/waterline/commit/0965d132 If themessagekey is not set on an error object, attempt to print the same output asconsole.login Node, by calling the object'sinspect()function, if it exists. We could try to fallback to callingutil.inspecton theerrobject and logging that, but I'm not sure the format would be appropriate.2.3.2 / 2015-09-08
2.3.1 / 2015-09-07
2.3.0 / 2015-08-31
strvariable for html coverage Order for variables definition is wrong in 3f78f10ca, so, html coverage page print<undefined></undefined>because str is undefined injade.compile(str, { filename: file });.nullandundefinedvalues in exports.typemake testsuggestion in https://github.com/mochajs/mocha/pull/1534#issuecomment-73151037