Getting Started tutorial fails to find test

[goser]

🐛 Bug Report

When following the getting started page step by step I get: No tests found, exiting with code 1

To Reproduce

Follow the steps on https://jestjs.io/docs/en/getting-started including yarn test

Expected behavior

Test success as described on https://jestjs.io/docs/en/getting-started

envinfo

System:
OS: Windows 10 10.0.17134
CPU: (12) x64 Intel(R) Core(TM) i7-8700 CPU @ 3.20GHz
Binaries:
Node: 12.14.1 - C:\Program Files\nodejs\node.EXE
Yarn: 1.21.1 - C:\Program Files (x86)\Yarn\bin\yarn.CMD
npm: 6.5.0 - C:\Program Files\nodejs\npm.CMD
npmPackages:
jest: ^26.2.1 => 26.2.1

I tried the same with jest@26.0.0 also not working.

jest@25.5.4 worked for me

[Radiateurs]

I have the same issue.
My jest.config.js is as follow :

module.exports = {
    verbose: true,
    collectCoverageFrom: [
        '<rootDir>/src/**/*.js',
        '!<rootDir>/node_modules/'
    ],
    testPathIgnorePatterns: [
        '<rootDir>/node_modules/'
    ],
    testMatch: [
        '**/__tests__/**/*.{js,jsx,mjs}',
        '**/+(*.)(spec|test).{js,jsx,mjs}'
    ]
};

Current file architecture :
/

|-> src/

|-> test/

|-> example.test.js

|-> package.json
|-> jest.config.jest

Could it be linked to #6546 ?

[jmtelljohann]

Are you sure it doesn't work in version 26.1.0? I just updated to 26.2.1 and Jest no longer finds my test (I use the default configuration for testMatch). If I downgrade to 26.1.0, it finds my tests again. It appears to be a Windows only issue because 26.2.1 finds my tests on Linux.

[ramram1048]

same issue for me, works on jest@25.5.4, not 26.1.0. my node version is v12.18.3

[goser]

No luck with 26.1.0

[jmtelljohann]

My issue was related to this and is fixed with 26.2.2: #10339

[github-actions]

This issue is stale because it has been open for 1 year with no activity. Remove stale label or comment or this will be closed in 30 days.

[github-actions]

This issue was closed because it has been stalled for 30 days with no activity. Please open a new issue if the issue is still relevant, linking to this one.

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.