Update "mocha" to version ~2.3.4 #17
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
marekventur
force-pushed
the
dependency-updater-mocha-to-2.3.4-1450130050451
branch
from
2733546
to
648a853
Compare
marekventur
added a commit
that referenced
this pull request
Jan 4, 2016
…1450130050451 Update "mocha" to version ~2.3.4
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
#2.3.4 / 2015-11-15
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.
Fix duplication of mocha.opts on process.argv
Fix typo in test/reporters/nyan.js
peinding -> pending
Better spritesheet hashing #2.3.3 / 2015-09-21
Relevant: breaks npm install -g npm in node 0.8 npm/npm#9668
Fix #1798: Correctly attribute mutiple done err with hooks
Stackfilter fix: Don't remove modules/components from stack trace in the browser
Revert jade to support npm < v1.3.7
Fix #1669: catch uncaught errors outside test suite execution
Unfortunately some frameworks throw error objects which do not have a
messageproperty but do have an
inspect()function. This means Mocha reports a testfailure, 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: balderdashy/waterline@0965d132
If the
messagekey is not set on an error object, attempt to print the sameoutput as
console.login Node, by calling the object'sinspect()function,if it exists.
We could try to fallback to calling
util.inspecton theerrobject andlogging that, but I'm not sure the format would be appropriate.
Fix fragile xunit reporter spec
Support all harmony flags
"Expected a conditional expression and instead saw an assignment"
Fix #1864: xunit missing output with --reporter-options output
Fix 1875: Markdown reporter exceeds maximum call stack size
Better spritesheet hashing #2.3.2 / 2015-09-08
Better spritesheet hashing #2.3.1 / 2015-09-07
Fix: Bail flag causes before() hooks to be run even after a failure
Better spritesheet hashing #2.3.0 / 2015-08-31
allows unhandled exceptions to propagate in the browser
added tests for allowUncaught option
global error handler prints to dom with allowUncaught
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.
Support --max-old-space-size node argument
Upgrade Jade dependency to 1.11.0
Jade syntax isn't broken in new version, but update some syntax
for being more explicitly. fix #1811
strvariable for html coverageOrder for variables definition is wrong in 3f78f10ca,
so, html coverage page print
<undefined></undefined>because str is undefined in
jade.compile(str, { filename: file });.Fix for async hook error handling issue
Decorate failed hook titles with test title
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
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.
Maximum call stack issue for large test suite
Remove TODO from Browserify transition
Fixes #1230
Closes #1727
Signed-off-by: Joshua Appelman jappelman@xebia.com
Closes #1193
Replace proto references with inherits module
Rework hook error tests to actually assert
Closes #1766
Closes #1767
Signed-off-by: Joshua Appelman jappelman@xebia.com
Stop runner sending SIGINT to itself from within SIGINT handler
Explicitly check
nullandundefinedvalues in exports.typesupport escaped spaces in cli options
Escape test/suite title for re in html reporter
Conflicts:
lib/reporters/html.js
Escape test/suite title for re in html reporter
Follows @boneskull's
make testsuggestion in[JSHINT] enabled on project mochajs/mocha#1534 (comment)