I think we ran into the same bug. What I had drilled this down to, was the jest runner being used. At some point, that switched from jest-jasmine2 to jest-circus.

If you set testRunner: 'jest-jasmine2' in jest.preset.js, your tests should succeed again.

But your details here, might help solve the underlying issue.

If you set testRunner: 'jest-jasmine2' in jest.preset.js, your tests should succeed again.

We already have this in our jest.preset.js and are experiencing this issue.

To add to this, the import order in the test file is significant. This only seems to happen when the jest-marbles import (or the import of another module which imports jest-marbles), is above the import from @ngrx/store/testing.

Works

import { MockStore, provideMockStore } from '@ngrx/store/testing';
import { cold, hot } from 'jest-marbles';

import { MockStore, provideMockStore } from '@ngrx/store/testing';
import { foo } from 'module-importing-jest-marbles';

Fails

import { cold, hot } from 'jest-marbles';
import { MockStore, provideMockStore } from '@ngrx/store/testing';

import { foo } from 'module-importing-jest-marbles';
import { MockStore, provideMockStore } from '@ngrx/store/testing';

I think we ran into the same bug. What I had drilled this down to, was the jest runner being used. At some point, that switched from jest-jasmine2 to jest-circus.

If you set testRunner: 'jest-jasmine2' in jest.preset.js, your tests should succeed again.

But your details here, might help solve the underlying issue.

Thank you so much. I was struggling with it for many days during dependencies upgrade. I also tried to use jasmine-marbles since it supports jest-circus, however, some of my tests were still failing, so enforcing using the jest-jasmine2 test runner solved the issue with failing marble tests.