ember-cli-blanket: `ember test` hangs without running tests

Steps to reproduce:

ember new testapp && cd testapp ember install ember-cli-blanket ember test

Then it will hang without running any tests: terminal_ phantomjs 85x52_and_new_issue sglanzer_ember-cli-blanket_and_slack_and_dashboard develop__222_commits

I’m on OSX.

“ember-cli-blanket”: “0.5.1”

Here’s my ember -v: version: 0.2.4 node: 0.12.2 npm: 2.9.1

I love this project and I’m happy to help if there’s anything I can do, but this may be a little over my head.

About this issue

  • Original URL
  • State: closed
  • Created 9 years ago
  • Comments: 20 (7 by maintainers)

Commits related to this issue

Most upvoted comments

Adding my voice, this is indeed an issue, my temporary workaround was to force the autostart to true in tests/index.html like this:

  <body>

    {{content-for 'body'}}
    {{content-for 'test-body'}}
    <script src="assets/vendor.js"></script>
    <script src="assets/test-support.js"></script>
    <script>
     /*
      * Force QUnit autostart to be true to work around changes in
      * ember-cli-qunit and ember-cli-blanket.
      *
      * Reference:
      * https://github.com/sglanzer/ember-cli-blanket/issues/60
      * https://github.com/ember-cli/ember-cli-qunit/commit/98c8d370d574adc4deb2ab438edd0d248b22155b
      */
      QUnit.config.autostart = true;
    </script>
    <script src="assets/app.js"></script>
    <script src="assets/blanket-options.js"></script>
    <script src="assets/blanket-loader.js"></script>
    <script src="testem.js"></script>
    <script src="assets/test-loader.js"></script>

    {{content-for 'body-footer'}}
    {{content-for 'test-body-footer'}}
  </body>

The two links in the reference show where there’s some conflict with how the autostart is preserved. Since ember-cli-qunit defaults to true but this isn’t reset until that timeout happens I feel like there’s a timing issue. A quick check shows that ember-cli-blanket sees the autostart set to false in blanket-require.js and so it’s set to false in start.js and so our tests don’t start.

Links: https://github.com/ember-cli/ember-cli-qunit/commit/98c8d370d574adc4deb2ab438edd0d248b22155b

@sglanzer looks like qunit autostart toggle issue - must have been a flip-flop in the new release.

in the browser if I run Qunit.start() it starts and runs

not sure where that toggle is taking place.

I’ll check mocha over the weekend