Angular test with asyncScheduler and flush - why it fails with flush()?
Asked Answered
T

1

8

There is this Angular component:

import { Component, OnDestroy, OnInit } from '@angular/core';
import { asyncScheduler, Observable, of, queueScheduler, scheduled } from 'rxjs';

@Component({
  selector: 'test-component',
  templateUrl: './test-component.component.html'
})
export class TestComponentComponent implements OnInit {
  value: string;

  constructor() { }

  ngOnInit(): void {
    const data$ = this.fetchDataScheduler();

    data$
      .subscribe(value => {
        this.value = value;
      });
  }

  private fetchDataScheduler(): Observable<string> {
    return scheduled(of('foo'), asyncScheduler);
  }

}

and the test is failing:

it('async - test setTimeout', fakeAsync(() => {
    expect(component.value).toBeFalsy();

    fixture.detectChanges(); // ngOnInit

    expect(component.value).toBeFalsy();
    flush();

    expect(component.value).toBe('foo');  // <- fails here
  }));

failing test

flush() should flush all macrotasks, but it does not. Why? If I use tick(), then the test is passing.

passing test

(Screenshots above provided by Jest and Wallaby plugin.)

Why is not passing with flush() but is passing with tick()?

flush:

Simulates the asynchronous passage of time for the timers in the fakeAsync zone by draining the macrotask queue until it is empty. The returned value is the milliseconds of time that would have been elapsed.

Repo is here: https://stackblitz.com/github/felikf/angular-testing-examples

Trulatrull answered 8/1, 2020 at 15:49 Comment(3)
Can you setup a stackblitz reproducing the problem? Based on the documentation, the tick() without arguments is a flush() command. angular.io/guide/testing#component-with-async-serviceLickerish
I am working on it: stackblitz.com/github/felikf/angular-testing-examples, it kind of works. It is possible to clone from github also.Trulatrull
Reported as bug: github.com/angular/angular/issues/34742Trulatrull
A
5

asyncScheduler is a setInterval which is a periodic macroTask, and currently the flush() API only flush non-periodic macroTasks such as setTimeout()

For now you should use tick() to make it work.

You can read more about it here

Anility answered 4/12, 2020 at 9:2 Comment(1)
See here and here - the referenced issue is mine, I have just forgotten to update answer, thank you for it.Trulatrull

© 2022 - 2024 — McMap. All rights reserved.