Maximilian Lenhardt

What I did was to put the `toBeObservable` Code inside the `toSatisfyOnFlush` block. But I agree, it is counterintuitive. ``` expect(stream$).toSatisfyOnFlush(() => { expect(stream$).toBeObservable(coldObservable); expect(mock).toHaveBeenCalledTimes(4); }); ```

I encountered the same issue in our Angular 12 project. Running all tests with ngneat/spectator at version 8.3.2 works fine, after upgrading to 9.0.0 I get the same error as...

Running into the same issue an Android wit the following SDK versions: minSdkVersion 23 targetSdkVersion 28 Sadly no way to figure out in which scenario this happens.

Sounds like a reasonable idea to make it configurable, but I feel it is rather redundant because you basically have the required information directly on the control: `this.ngControl.control?.updateOn` is either...

I got a working solution which I would like to discuss, so yes. For some reason I do not understand the solution I posted originally worked for a while and...

See the attached PR. Any help with the issue described there is appreciated.

> I came here for the same problem, I followed your suggestion @Blafasel3, but when inside the `toSatisfyOnFlush()`, the `expect().toBeObservable()` always pass, whatever the coldObservable I'm testing... > > For...

I know this is quite old, but I stumbled over this while googling and as I udnerstand the question, doing this in each test would help: ``` it('', () =>...

One solution for Maps could be: ``` if (a instanceof Map && b instanceof Map) { return isEqual(Object.fromEntries(a), Object.fromEntries(b)); } ```

@thomasjahoda not sure if this is maintained anymore, but maybe open a PR?