In January, 2015 I published the jasmine-precondition project on GitHub. This project aims to implement a Jasmine instruction to ease setting up asynchronous pre-conditions before, during and after tests.
Since Jasmine 2.0, the runs, waits, and waitsFor methods have been removed in favor of allowing functions run as part of the spec to receive and invoke a done callback. This new approach is described at Upgrading Jasmine - Asynchronous Specs.
The done callback works great for asynchronous features with a callback (such as AJAX, jQuery animations or anything else with promises). However, there are yet other asynchronous features that will complete on their own and would be using waitsFor before Jasmine 2.0, like rendering Google Maps, images or anything else that can change both the DOM and the CSSOM.
While it is utterly possible to re-implement waitsFor I believe that Jasmine 2.0 direction is more towards stepping away from this idea and instead taking more advantage of done callbacks, like putting one it block as a pre-condition for another.
Thus, the preCondition instruction defined here will simply poll a given conditional function at a certain time interval, and once its condition is met the callback done will be fired off.
To the date, its version 0.1.0 can be used either standalone and through node.js, available on NPM.
Travis CI status:
preCondition(condition, done, interval);
- condition: a conditional function that shall only return true when the condition you are expecting for is met.
- done: the done callback from beforeEach, it or afterEach must be passed here.
- interval (optional): a time interval in milliseconds between two condition executions. Default is 100.