You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm guessing because it just assumes no one mucks with the global setTimeout methods. In particular, running the following using wct
suite('AwesomeLib',function(){this.timeout(1000);setup(function(){this.clock=sinon.useFakeTimers();});teardown(function(){this.clock.restore();});test('is awesome',function(done){// ... assume we do something async here.flush(function(){assert.isTrue(true);done();});});});
results in mocha failing the test with error "timeout of 1000ms exceeded".
Perhaps the fix is to do something like what Mocha did (capture the desired global timer methods): mochajs/mocha#237
The text was updated successfully, but these errors were encountered:
I'm guessing because it just assumes no one mucks with the global setTimeout methods. In particular, running the following using wct
results in mocha failing the test with error "timeout of 1000ms exceeded".
Perhaps the fix is to do something like what Mocha did (capture the desired global timer methods): mochajs/mocha#237
The text was updated successfully, but these errors were encountered: