Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Test file found by "testMatch" but somehow nothing found in "Pattern"
See original GitHub issueCurrent Behavior
I create a brand new project by running “npx tsdx create” and run “npm test” but no test file is found, see screenshot:
We can see that one test file was found at the beginning:
testMatch: **/__tests__/**/*.[jt]s?(x), **/?(*.)+(spec|test).[tj]s?(x) - 1 match
Expected behavior
Test file should be found.
Suggested solution(s)
Additional context
Your environment
| Software | Version(s) |
|---|---|
| TSDX | 0.12.3 |
| TypeScript | 3.7.5 |
| Browser | |
| npm/Yarn | npm 6.13.7 |
| Node | v12.1.0 |
| Operating System | OSX 10.15.3 |
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:5
Top Results From Across the Web
Jest No Tests found - Stack Overflow
No tests found In /usr/src/app says that Jest is looking for tests ... have in jest.config.js the following pattern for testMatch property:
Read more >wrong test pattern when running single Jest test, 'no tests found'
No tests found. In C:\WebstormProjects\untitled4 4 files checked. testMatch: **/__tests__/**/*.js?(x),**/?(*.)(spec|test).js?(x) - 1 match
Read more >Strengthening Forensic Science in the United States
fingerprint found on a gun may be used to determine whether a defendant handled the weapon; drug analysis ... But nothing in Daubert...
Read more >FINANCIAL CRISIS - GovInfo
quences but also in damage to the trust of investors, businesses, and the public in the financial system. For example, our examination found,...
Read more >National Guidelines for Behavioral Health Crisis Care
tested best-practice guidance to the behavioral health field. ... You will also find innovative data-informed crisis system capacity ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Just updating here that https://github.com/lukeed/sade/pull/36 was merged within ~10 hours of me making it and was released in
sade@1.7.3 .Because the bug was upstream, no updates to TSDX itself are necessary. To get this fix in
tsdxyou just need re-install (npm i tsdx). The 1.7.2 -> 1.7.3 bump will be in yourpackage-lock.json(oryarn.lock). All new installs will have the latest version ofsadeby default.This issue can be closed as it’s been resolved.
Sent a PR upstream: https://github.com/lukeed/sade/pull/36
Hopefully the root cause is resolved upstream soon.
TSDX could pin
sade@1.7.0 as well as a stop-gap, but Jared is behind on releases and merges and that would only solve the bug for those who upgraded TSDX to latest, all older versions would get this bug if it’s not patched upstream.