Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"yeoman test" freezes #648

Closed
eirslett opened this issue Oct 19, 2012 · 3 comments · Fixed by #652
Closed

"yeoman test" freezes #648

eirslett opened this issue Oct 19, 2012 · 3 comments · Fixed by #652

Comments

@eirslett
Copy link
Contributor

mkdir yeomantest
cd yeomantest
yeoman init
yeoman test

I'm running the commands inside a VM on Linux Mint, bundled with Firefox 12.

When running the tests through the browser (index.html) I get this error: mochajs/mocha#549

When I run them through yeoman (yeoman test) it just freezes.

The issue was fixed for mocha version 1.4.1, but yeoman is using mocha 1.4.0.

Solution: Yeoman should upgrade the mocha dependency, at least to 1.4.1, or maybe even to the current latest version (1.6.0)

That should solve this particular problem, but more generally - if there's a javascript error in the browser, "yeoman test" freezes completely. Is there a way to detect that, and abort execution?

@eirslett
Copy link
Contributor Author

Looks like it's grunt-mocha that has the problem...

@eirslett
Copy link
Contributor Author

Hmm... "yeoman test" works for me on my Windows 7 host system (yeoman 0.9.4), but the tests still fail in Firefox. So the two problems are probably unrelated. I suspect my VM was running an old version of yeoman though, so the freeze problem might be solved by now.

@sindresorhus
Copy link
Member

Grunt-mocha was updated in 0.9.5

addyosmani pushed a commit that referenced this issue Apr 24, 2015
Which should in turn upgrade version of mocha.
Hopefully fixes #648
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants