Using run(), and waits() methods #56

New Issue

2011-08-20T21:17:27Z

lporras commented

2011-08-20 21:17:27 +00:00

(Migrated from github.com)

I have a spec file where I have 2 calls to run(), and a waits(15500), when I run this spec I get this message: WARNING: too many runs and the test is still not finished!, I found that if I reduce the number of milliseconds in the waits() method until 5457 the tests passed, with a greater number the messages appear

johnbintz commented

2011-08-22 13:10:07 +00:00

(Migrated from github.com)

There's a magic number timeout in the spec runner, a holdover from its earlier days. I'll take a closer look into it later this week and come up with a solution, probably a combination of being able to provide a timeout and a way for Jasmine to notify the runner that it's still alive and not locked.

johnbintz commented

2011-09-06 15:39:37 +00:00

(Migrated from github.com)

See if that works better for you. The runner always times out if nothing happens after five second, but waits and waitsFor pause that internal timer.

See if that works better for you. The runner always times out if nothing happens after five second, but `waits` and `waitsFor` pause that internal timer.

johnbintz commented

2011-09-12 12:53:00 +00:00

(Migrated from github.com)

I'm gonna close this, it's working fine in the tests. If you are still having issues, reopen this, er, issue.

Sign in to join this conversation.