Called start() outside of a test context
See original GitHub issueNot sure if this belongs here or somewhere else, but I’m running into this error while using ember-qunit 0.2.8. When running tests in ember-cli, I’m getting a JSHint global error:
JSHint - views: global failure
Uncaught Error: Called start() outside of a test context while already started
Source: http://localhost:4200/assets/test-support.js:2559
Any suggestions for troubleshooting this?
Issue Analytics
- State:
- Created 9 years ago
- Comments:11 (4 by maintainers)
Top Results From Across the Web
Running QUnit (TypeScript) tests with Chutzpah gives "Called ...
Running QUnit (TypeScript) tests with Chutzpah gives "Called start() outside of a test context while already started" · javascript · visual-studio ...
Read more >Queueable apex still executes in test context even if Enqueue ...
Queueable apex still executes in test context even if Enqueue Job is not called between Test. startTest() and Test. stopTest() - Salesforce ...
Read more >Testing - Spring
TestSocketUtils is a simple utility for finding available TCP ports on localhost for use in integration testing scenarios. TestSocketUtils can ...
Read more >Testing Apollo Client Applications - Apollo GraphQL Blog
Start at the very outer boundary of the application — and in the context of a client-side web application, that usually means starting...
Read more >The Testing Context - .NET Core Tutorials
That is, if they are testing one particular class, let's say ServiceA, and that has a method that calls ServiceB. Your test actually...
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
If it helps anyone, we just started having this issue and in our case it was caused by ember-cli-blanket which is currently broken with qunit >= 2.2.2. See the blanket issue for details.
This issue was also hiding/breaking the “Module” dropdown on the
localhost:4200/tests
page, which was weird.The temporary solution, as an alternative to removing blanket entirely, is to change
autostart
to false in the blanket options.@workmanw yeah it took me a long time to narrow it down, glad I could spare someone else that pain