You could do one of two things:
1: Actually wait in the test 250+1 ms in a setTimeout()
, then check if the element actually disappeared.
2: use fakeAsync()
and tick()
to simulate time in the test - a tick()
will resolve the setTimeout in the original close()
, and the check could happen right after in a fixture.whenStable().then(...)
.
For example:
it("tests the exit button click", fakeAsync(() => {
comp.close()
tick(500)
fixture.detectChanges()
fixture.whenStable().then(() => {
const popUpWindow = fixture.debugElement.query(By.css("#popup-window"))
expect(popUpWindow).toBe(null)
})
}))
I suggest using the 2nd one, as it is much more faster than actually waiting for the original method. If you still use the 1st, try lowering the timeout time before the test to make the it run faster.
SEVICES
For services you do not need to call detectChanges
after tick
and do not need to wrap the expect statements within whenStable
. you can do your logic right after tick
.
it('should reresh token after interval', fakeAsync(() => {
// given
const service: any = TestBed.get(CognitoService);
const spy = spyOn(service, 'refreshToken').and.callThrough();
....
// when
service.scheduleTokenRefresh();
tick(TOKEN_REFRESH_INTERVAL);
// then
expect(spy).toHaveBeenCalled();
}));
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…