-
-
Notifications
You must be signed in to change notification settings - Fork 6.5k
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
Consider upgrading to Jasmine 2 #74
Comments
👍 |
This would be great - being able to use done() for async testing would really be welcome! |
Any news on that? Ironically, I've found that exactly the tests I moved from plain Jasmine to Jest for in order to simplify my tooling - CSP code that requires ES6 generators - don't work any longer. |
👍 |
I agree! 👍 |
👍 I actively use CSP (via js-csp), so it would be pretty nice if I could do something like this: go(function *() {
var value;
value = yield take(makeAsyncThing());
expect(value).toEqual('whatever');
done();
}); |
👍 +1 |
👍 @jeffmo How do you think |
👍 |
2 similar comments
👍 |
👍 |
Yeah, we need it! 👍 |
👍 |
3 similar comments
👍 |
👍 |
👍 |
Upgrading to Jasmine 2 would also fix equality issues like the one demonstrated here: https://gist.github.com/randymorris/439a85bccc856ca4e8c1. |
(thumbsup) |
related question: Has anyone dropped in 2.x to see what happens? may not be too bad to fix. OSS and all... (puts on todo list) |
👍 |
2 similar comments
👍 |
👍 |
@robrobbins Tried that yesterday. Wanted to limit the amount of time I spent doing it (time boxed to an hour). It's not a simple replacement. I also realized (shortly after) that the jest team would have done this if it was that easy. 👍 |
👍 |
Just wanted to follow up here to say that I don't have any immediate plans to build out Jasmine2 support, but only for lack of cycles myself. However, if someone wanted to take a crack at building a You can take a look at the existing It should be possible to build a https://github.com/facebook/jest/blob/master/src/lib/utils.js#L29 |
Here is WIP update to jasmine 2.x: #330 Help wanted. |
I was struggling for an hour wondering why my done() wasn't working... ;__; |
Thank you for reporting this issue and appreciate your patience. We've notified the core team for an update on this issue. We're looking for a response within the next 30 days or the issue may be closed. |
Well, sir Bot, it's quite a relevant issue still 🍰 but human beings seem to be aware of that wrt #330 |
Yes yes, we are working on this. There is a lot of work that we need to do to make jest awesome and I'm still working through the backlog of things we need to do at Facebook. Please have a little bit more patience and I will make sure jest is great soon! (I assigned this issue to me, hoping that will shut up our bot. cc @vjeux) |
Oh I'm very patient @cpojer, I just wanted to interact with that inquiring bot of yours :) |
jest 0.8.0 was published just now with optional jasmine2 support! Thanks everyone and I'm deeply sorry for the long wait. |
Thank you so much for Jasmine 2 support ! |
@cpojer how do I specify this in the command line? I tried this but I still get jasmine1 being used "scripts": {
"test": "jest -testRunner = 'node_modules/jest-cli/src/testRunners/jasmine/jasmine2.js"
},
Using Jest CLI v0.8.2, jasmine1
|
@quantuminformation
https://github.com/catalin-enache/ab_utils/blob/master/package.json |
You need |
I couldn't get --testRunner to run. I needed the extended one. |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Async support in Jasmine 1.3 is pretty poor, this has been fixed in version 2 of the framework. Maybe we should consider upgrading to that version.
The text was updated successfully, but these errors were encountered: