Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Page reloads without finishing tests #547

Closed
luketheobscure opened this issue Apr 23, 2015 · 6 comments · Fixed by #550
Closed

Page reloads without finishing tests #547

luketheobscure opened this issue Apr 23, 2015 · 6 comments · Fixed by #550

Comments

@luketheobscure
Copy link

When running the testem server and accessing the runner in the browser, the page reloads over and over again, without ever finishing the tests.

It seems to be due to this method, which I think is fired in response to a socket.io method:

function startTests(){
  socket.disconnect()
  parent.window.location.reload()
}

I'm happy to provide more information, and would love some debugging advice if you think it's a bug in my setup. If it helps, this is a test suite for a very (very) large Ember.js app, using QUnit as the testing framework.

@goneplaid
Copy link

I have the same setup and have experienced this issue as well. I ended up just using npm test to run things from the console but testing in the browser would be really nice for debugging purposes.

@johanneswuerbach
Copy link
Member

I'll take a look. Just to double check, which os / node / testem version are you running?

@luketheobscure
Copy link
Author

Node: v0.12.2
NPM: v2.1.6
Testem: v0.8.2
OSX 10.10.2

Thanks!

@johanneswuerbach
Copy link
Member

This should be fixed by #550. Could you add "disable_watching": true to your testem.json?

@johanneswuerbach
Copy link
Member

ember-cli PR ember-cli/ember-cli#3962

@luketheobscure
Copy link
Author

That fixed it. You're awesome.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants