feat: support jest-circus

[L2jLiga]

Created generic addMatchers function which will handle Jasmine vs Jest ways

Signed-off-by: Andrey Chalkin L2jLiga@gmail.com

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our guidelines: https://github.com/ngneat/spectator/blob/master/CONTRIBUTING.md#commit
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, local variables)
[x] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Other... Please describe:

What is the current behavior?

Issue Number: #314

What is the new behavior?

Use expect.extend from Jest to add custom matchers.

Does this PR introduce a breaking change?

[ ] Yes
[x] No

Other information

[NetanelBasal]

Thanks for the PR. I'm not familiar with jest-circus. Can you give me some background about the fix?

[L2jLiga]

I just noticed that I did not fix all - spies does not work. - seems to be ok

In this fix I introduced new file test-framework.ts (not sure is it fine enough name for it) which goal is to solve cross-framework issues like jasmine.addMatchers VS expect.extend in Jest and use it as framework independend API

[NetanelBasal]

Yes, but what is the difference between jest and jest-circus that we need to add this fix?

[L2jLiga]

Afaik jest have bundled jest-jasmine package and it enabled in default test runner while jest-circus is new runner which does not provide such functionality by default, especially global jasmine variable

[NetanelBasal]

Great, so we are sure it'll not cause any regressions, right?

[L2jLiga]

No changes for Jasmine and expect.extend exsists in Jest for very long time. I think so

[NetanelBasal]

Cool, thanks.