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

Support it.only or iit #1

Closed
juliemr opened this issue Jul 19, 2013 · 3 comments
Closed

Support it.only or iit #1

juliemr opened this issue Jul 19, 2013 · 3 comments

Comments

@juliemr
Copy link
Owner

juliemr commented Jul 19, 2013

These features will be available in Jasmine 2.0, but it would be nice to have them in the meantime.

@searls
Copy link
Contributor

searls commented Sep 16, 2013

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 it.only (see "4 tests, 1 assertion")?

....

Finished in 0.004 seconds
4 tests, 1 assertion, 0 failures

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

@juliemr
Copy link
Owner Author

juliemr commented Oct 1, 2013

Awesome, thanks for this workaround!

@juliemr
Copy link
Owner Author

juliemr commented Dec 6, 2013

Closed in 0.2.6

@juliemr juliemr closed this as completed Dec 26, 2013
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

No branches or pull requests

2 participants