bug: Unable to run Jest spec files from subdirectory or absolute path

[sean-perkins]

Prerequisites

• I have read the Contributing Guidelines.
• I agree to follow the Code of Conduct.
• I have searched for existing issues that already report this problem, without success.

Stencil Version

v2.19.2

Current Behavior

When running stencil test --spec in Ionic Framework (main), we are only able to run tests for the entire src/utils directory with the following command:

stencil test --spec --max-workers=2 src/utils/

If we provide an additional sub directory or absolute path to our spec file, we receive the following error:

  ● Test suite failed to run

    TypeError: virtualMocks.get is not a function

      at Resolver._getVirtualMockPath (node_modules/@jest/core/node_modules/jest-resolve/build/resolver.js:468:25)

This occurs with any of the following:

stencil test --spec --max-workers=2 src/utils/keyboard/

stencil test --spec --max-workers=2 src/utils/keyboard/test/keyboard.spec.ts

The test runs and passes correctly if we run from src/utils.

Expected Behavior

Developers should be able to run the stencil test --spec command with any valid directory or absolute path and the spec files should execute consistently; regardless of if ran exclusively or as part of a larger directory.

Steps to Reproduce

1. Clone Ionic Framework
2. Checkout main branch
3. Run npm run test.spec src/utils
4. Observe: Tests run successfully
5. Run npm run test.spec src/utils/keyboard
6. Observe: Tests fail with the error mentioned above

Code Reproduction URL

https://github.com/ionic-team/ionic-framework

Additional Information

No response

[rwaskiewicz]

npx stencil test --spec --max-workers=2 src/utils/keyboard works, but npm run test.spec -- src/utils/keyboard and npm run test.spec src/utils/keyboard do not 🤔

[alicewriteswrongs]

found a few issues which might be related: playwright-community/jest-playwright#665 and jestjs/jest#11267 (comment)

Unfortunately upgrading Jest in framework doesn't fix it :/

[alicewriteswrongs]

also I've found that in addition to the commands @rwaskiewicz mentioned above, the following works:

npx stencil test --spec --max-workers=2 src/utils/keyboard/test/

while the following does not

npx stencil test --spec --max-workers=2 src/utils/keyboard/test

the only difference being the trailing slash. So something odd is going on here!

[alicewriteswrongs]

Ok so this is actually some sort of caching thing, I think on Jest’s side of things but I’m not sure.

Basically if you run a command like this one multiple times in a row:

npx stencil test --spec --max-workers=2 src/utils/keyboard

it will alternate between running correctly and failing. The same applies for doing npm run tsc.spec , passing other sub-directories, etc.

[alicewriteswrongs]

Aaaallright so the issue was caused by having different versions of @jest/core, on the one hand, and jest and jest-cli on the other. I updated jest and jest-cli in a branch in Framework to match the version of @jest/core (27.5.1) and can no longer reproduce the issue.

[rwaskiewicz]

Closing, as we received feedback from the Framework team that ionic-team/ionic-framework#26320 resolved the issue