Cannot run tests
See original GitHub issueHello! I just freshly cloned this repo and did yarn && yarn test
. Here’s the error:
❯ node -v
v10.6.0
❯ yarn test
yarn run v1.3.2
$ mocha --globals document test
internal/modules/cjs/loader.js:583
throw err;
^
Error: Cannot find module '../../build'
at Function.Module._resolveFilename (internal/modules/cjs/loader.js:581:15)
at Function.Module._load (internal/modules/cjs/loader.js:507:25)
at Module.require (internal/modules/cjs/loader.js:637:17)
at require (internal/modules/cjs/helpers.js:20:18)
Issue Analytics
- State:
- Created 5 years ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
Tests not running in Test Explorer - visual studio
This was my problem, too. In VS 2019, it doesn't seem to happen with Xunit, though. But it always occur when using MsTest...
Read more >Can't run or debug unit tests - Visual Studio Feedback
I'm using Visual Studio Community Edition 15.8.1 and I can't run or debug any unit tests. Every time I'm trying to run the...
Read more >Cannot run Unit Tests | Apple Developer Forums
1. Open project in Xcode which has unit tests · 2. Open the Test navigator · 3. Click a run button to run...
Read more >How To Resolve Issue Of Test Project Not Running The Unit ...
Two of my test projects didn't run the test cases, it was about to start and took some time to run the test...
Read more >Tests not running in Visual Studio - Developers Log
[Warning] No test is available in xxx.dll. Make sure that test discoverer & executors are registered and platform & framework version settings ......
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
Oh, that’s better. Thanks so much - sorry about the issue spam.
Hey @benswift, seems you are missing the
-t
option (it defaults tobrowser
, which is why it’s failing.)Try:
Alternatively, try with
-t node
(target):