2.0.0-beta3: Cannot find module './src/jasmine-matchers'

[jamiemason]

2.0.0-beta3: Cannot find module './src/jasmine-matchers'

[reintroducing]

That worked perfectly @JamieMason, thank you and thanks for this module, it's been a huge help when writing Jasmine tests previously and now with using Jest as well.

[JamieMason]

Apologies, this was missing. I've fixed this and released 2.0.0-beta4.

[Szpadel]

Hello @JamieMason

I have beta4 installed and the issue is still present.
Could you double check this?

[mull]

I also saw this failing for beta4

[JamieMason]

You're right @Szpadel @mull. Addressing it now, sorry about this.

[mull]

No worries. I can test this within the next ~3 hrs (or tomorrow), let me know when you release and I'll see if it works :)

[JamieMason]

Just published [email protected]

shakes head normally I'm more thorough, but I rushed this.

[JamieMason]

karma-jasmine-matchers updated to 2.0.0-beta5 as well.

[Szpadel]

With beta5 it's working fine, thanks.

[mull]

Works. Though I ran into a small problem, for some reason, that Jest started auto-mocking the module all of a sudden. It didn't before. Anyhow, I just added it to the list of unmocked packages and all is fine. Thanks for the work @JamieMason!

[JamieMason]

Phew, great.

@mull would you mind showing how Jasmine-Matchers can be used with Jest? Someone mentioned before that they're compatible, but I've never seen for myself how it works.

Thanks.

[mull]

@JamieMason sure.

// package.json
"unmockedModulePathPatterns": [
  "jasmine-expect"
],

//some test
import JasmineExpect from 'jasmine-expect';

...
  expect(uniList).toBeNonEmptyArray();
  expect(uniList).toBeArrayOfObjects();

Not any harder than that. AFAIK we're doing nothing special :-) We're moving away from Jest though, absolutely hate it!

[JamieMason]

Thanks a lot @mull that's useful (may add it to the README). We looked at Jest at work for a while but decided against it in the end. The idea of automatic mocking though did sound like it could be quite nice.

[mull]

No problem! It is kind of nice sometimes. Jest is buggy though, and some of the options in the docs don't quite work. Especially combined with other options (one is somehow overriding the other.) It's been a messy journey so far.

[reintroducing]

Is there any way to do this in a test-setup.js file that is executed with the setupFiles command from Jest? I'd like to just import this once and not have to worry about it in every single test file.

As of right now the only way I can get this working is to do this in each test file:

import JasmineExpect from 'jasmine-expect'; // eslint-disable-line no-unused-vars

It's kind of tedious and I expect another developer on the team will forget at some point and wonder why his tests are failing.

[JamieMason]

I'll push an example up soon but the config you need I think @reintroducing is setupTestFrameworkScriptFile

{
  "devDependencies": {
    "jasmine-expect": "*",
    "jest": "18.1.0"
  },
  "jest": {
    "setupTestFrameworkScriptFile": "<rootDir>/node_modules/jasmine-expect/index.js",
    "verbose": true
  },
  "private": true,
  "scripts": {
    "test": "jest"
  }
}

[JamieMason]

Example added: 12e464c.

[JamieMason]

You're welcome, thanks.