toBeVisible-matcher does not work with jest

[askarby]

I'm submitting a...

[ ] Regression (a behavior that used to work and stopped working in a new release)
[x] Bug report
[ ] Performance issue
[ ] Feature request
[ ] Documentation issue or request
[ ] Support request
[ ] Other... Please describe:

Current behavior

Visible elements are reported as "not being visible" by the toBeVisible-matcher, when spectator is used within jest (using the @ngneat/spectator/jestdependency).

Expected behavior

Visible elements should be reported as "being visible"

Minimal reproduction of the problem with instructions

A minimal reproduction repository can be found here: https://github.com/askarby/jest-tobevisible-bug

What is the motivation / use case for changing the behavior?

You would expect the matcher to work, used in jest or jasmine alike.

Environment

Angular version: 9.0.3

Browser:

- [ ] Chrome (desktop) version XX
- [ ] Chrome (Android) version XX
- [ ] Chrome (iOS) version XX
- [ ] Firefox version XX
- [ ] Safari (desktop) version XX
- [ ] Safari (iOS) version XX
- [ ] IE version XX
- [ ] Edge version XX
- [x] jsdom

For Tooling issues:

• Node version: 10.17.0
• Platform: Mac

Additional Details

The problem seems to be related to the issue: jsdom/jsdom#135 (regarding jsdom not being able to determine offsetHeight, offsetWidth, etc (which is used from within the toBeVisible-matcher).

[NetanelBasal]

I'm not sure what you mean. Both Jasmine and Jest are using the same toBeVisible matcher.

[askarby]

@NetanelBasal

True.... but the implementation of toBeVisible only works (as intended) with jasmine... it fails when used with jest!

Visible elements are reported as being hidden (not visible)

NOTICE: I updated the issue report to be more concise.

[NetanelBasal]

Feel free to investigate and create a PR.