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

Note: jasmine2 does not yet support per-spec timeouts #1701

Closed
juliemr opened this issue Jan 8, 2015 · 3 comments
Closed

Note: jasmine2 does not yet support per-spec timeouts #1701

juliemr opened this issue Jan 8, 2015 · 3 comments
Milestone

Comments

@juliemr
Copy link
Member

juliemr commented Jan 8, 2015

In Jasmine 1.3, you can do:

it('does stuff', function() {
  ...
}, 100);

To specify a timeout of 100 ms.

Jasmine2 has added this feature in master (jasmine/jasmine@a4faa80) but it is NOT YET released in version 2.1.1.

This causes npm test to fail for Protractor's own test because our timeout suite (expected to fail) instead passes.

TODO - close this issue when a new version of Jasmine is released.

@juliemr juliemr modified the milestone: Pending Mar 17, 2015
@juliemr
Copy link
Member Author

juliemr commented May 20, 2015

Done, now that we've upgraded to Jasmine 2.3.

@juliemr juliemr closed this as completed May 20, 2015
@prabhu-telsiz
Copy link

@juliemr

Im using
"jasmine": "2.3.1"
"Protractor: Version 2.1.0"

it('does stuff', function() {
...
}, 1000);

I tried this and I got this error.

Jasmine spec timed out. Resetting the WebDriver Control Flow.
" Error: Timeout - Async callback was not invoked within timeout specified by jasmine.DEFAULT_TIMEOUT_INTERVAL."

But the same spec used to work before updating protractor and Jasmine.

@donaldpipowitch
Copy link

I have problems with jasmine.DEFAULT_TIMEOUT_INTERVAL, too. No matter how I write my code... I can't get rid of it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants