fixture.detectChanges() leads to unresolvable Problem in fakeAsync zone

Angular Version: 12

“ngx-quill”: “^14.3.0”, “quill”: “^1.3.7”,

The problem is pretty easy to reproduce. Create a test component containing any quill instance.

Then if you do

beforeEach(() => {
  fixture.detectChanges()
})

everything works fine.

However if you do:

beforeEach(fakeAsync(() => {
  fixture.detectChanges();
});

it will always fail with a timer still in queue problem.

[activenode]

Unfortunately no. We did do a workaround but it’s pretty “over-engineered” IMO:

Apparently quill/ngx-quill needs fixture.detectChanges() to be ran outside of fakeAsync to ensure proper loading.

But that also triggers ngOnInit. Hence we do this:

// 1. catch the init call to avoid the actual call
const initSpy = spyOn(component, 'ngOnInit');

// 2. detectChanges for ngx-quill
fixture.detectChanges();

// 3. fall back again
initSpy.and.callThrough()

[KillerCodeMonkey]

Strange because I do not have any problems in my unit tests.

There are some with fakeasync as well.

Since this project is growing over years I forget some implementation details 😃.

I knew that there is an optional debounce timer for change detection in the editor.

Maybe this debouncing is running and you need to add a tick() with some milliseconds as Parameter.

David Lorenz @.***> schrieb am Do., 25. Nov. 2021, 08:50:

Unfortunately that does not help. We tried multiple different ways.

[image: image] https://user-images.githubusercontent.com/9058762/143400857-9db92093-4633-4d23-949f-8bbe28f4f536.png

Feel free to clone the above sample repo.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/KillerCodeMonkey/ngx-quill/issues/1425#issuecomment-978919006, or unsubscribe https://github.com/notifications/unsubscribe-auth/AARI4YDA2PFMQL4UII7XURLUNXTEXANCNFSM5IWSFAJQ .