-
Notifications
You must be signed in to change notification settings - Fork 20
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
Support it.only or iit #1
Comments
Hey @juliemr. It might interest you to know that I just pushed a working jasmine-only to npm and it works in conjunction with minijasminenode just fine (one just needs to do `require('jasmine-only') from a spec helper so that it can monkey-patch the global jasmine goods). The output is a little silly, though. Here's a suite with 4 specs but only the third one is actually being run with
So that is to say it "works" now, but it's not abundantly obvious to the user that it's working. I suspect your custom reporter would just need to be tweaked to exclude non-asserting tests. If you need an example feel free to ask |
Awesome, thanks for this workaround! |
Closed in 0.2.6 |
These features will be available in Jasmine 2.0, but it would be nice to have them in the meantime.
The text was updated successfully, but these errors were encountered: