a1011e7748
- THere seems to be a performance regression. Large test suites may throw - Regressions: Mock Clock won't install correctly, async specs are temporarily not supported. - Async spec runs/waits interface is gone. Blocks are gone. - Move most global usage into jasmine.Env constructor. - Remove optional 'Jasmine running' from HtmlReporter -- caused NS_FACTORY_ERROR in firefox when tested
41 lines
1.2 KiB
JavaScript
41 lines
1.2 KiB
JavaScript
//// TODO: Disabling b/c this spec isn't testing what it thinks it is.
|
|
//// Make a proper unit and intergration tests for this object
|
|
//describe("MockClock", function () {
|
|
//
|
|
// beforeEach(function() {
|
|
// jasmine.Clock.useMock();
|
|
// });
|
|
//
|
|
// describe("setTimeout", function () {
|
|
// it("should mock the clock when useMock is in a beforeEach", function() {
|
|
// var expected = false;
|
|
// setTimeout(function() {
|
|
// expected = true;
|
|
// }, 30000);
|
|
// expect(expected).toBe(false);
|
|
// jasmine.Clock.tick(30001);
|
|
// expect(expected).toBe(true);
|
|
// });
|
|
// });
|
|
//
|
|
// describe("setInterval", function () {
|
|
// it("should mock the clock when useMock is in a beforeEach", function() {
|
|
// var interval = 0;
|
|
// setInterval(function() {
|
|
// interval++;
|
|
// }, 30000);
|
|
// expect(interval).toEqual(0);
|
|
// jasmine.Clock.tick(30001);
|
|
// expect(interval).toEqual(1);
|
|
// jasmine.Clock.tick(30001);
|
|
// expect(interval).toEqual(2);
|
|
// jasmine.Clock.tick(1);
|
|
// expect(interval).toEqual(2);
|
|
// });
|
|
// });
|
|
//
|
|
// it("shouldn't complain if you call jasmine.Clock.useMock() more than once", function() {
|
|
// jasmine.Clock.useMock();
|
|
// });
|
|
//});
|