Unit tests fail because of the following issue: jestjs/jest#4407:

Using .toThrowErrorMatchingSnapshot() on code that prints error using ansi codes (i.e. using chalk) produces different snapshots if run locally or on CI.

There is a workaround proposed:

https://github.com/joaogranado/jest-serializer-ansi

However, it still fails for us with a really interesting output:

jest-console › console.error › toHaveErroredWith works when not called
[1]
[1] expect(value).toMatchSnapshot()
[1]
[1] Received value does not match stored snapshot 1.
[1]
[1] Compared values have no visual difference.
[1]
[1] 47 | expect(
[1] 48 | () => expect( console ) matcherNameWith
[1] > 49 | ).toThrowErrorMatchingSnapshot();
[1] 50 | } );
[1] 51 |
[1] 52 | test( ${ matcherNameWith } works with many arguments that do not match, () => {
[1]
[1] at Object. (packages/jest-console/src/test/index.test.js:49:8)

In particular Compared values have no visual difference. is puzzling.