Error while running tests
See original GitHub issueI added react-storybook to a project with react-boilerplate. When I try to run tests I get this error
Uncaught Error: dataId is not supplied via queryString at webpack:///~/@kadira/storybook/dist/client/preview/index.js:64:0 <- test-bundler.js:54610
Has anyone experienced this issue or know what it belongs to?
Issue Analytics
- State:
- Created 7 years ago
- Comments:7 (3 by maintainers)
Top Results From Across the Web
Error while running tests: TypeError: Cannot read property ...
Issue Type: Bug. Behaviour. I've read through the various issues but am seeing the given problem again that when looking at the consoles ......
Read more >Unit tests run in Test Explorer despite build error and I click ...
Developer Community. When initiating test execution in Test Explorer, if my code has a build error I get the expected dialog stating “There...
Read more >How to prevent Jest from running tests when an error occurred
I tried calling fail() from setup code - in beforeEach() in my case - but the test still runs (and fails) as does...
Read more >Handling the Error 'The test run has stopped...'
To view the test commands that posted the error message, double-click that message in the test log. TestComplete will open the test containing...
Read more >'Could not run tests on class ' error is returned for some ...
Users receive the error "Could not run tests on class <classId>" where classId is a specific class ID, when running all the test...
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 FreeTop 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
Top GitHub Comments
@arunoda I will create an example soon when I have time
Gonna close this since the original issue has been fixed.