defunctzombie / zuul

[UNMAINTAINED] multi-framework javascript browser testing
958 stars 87 forks source link

Automatically re-run tests on code changes #180

Open andreypopp opened 9 years ago

andreypopp commented 9 years ago

It would nice to have tests automatically re-run as code changes.

rase- commented 9 years ago

You can refresh the browser to run tests with the current files (including any changes made since last run). Did you mean to have tests run even without a refresh on every change?

andreypopp commented 9 years ago

Yes

On Sun, Mar 29, 2015, 05:45 Tony Kovanen notifications@github.com wrote:

You can refresh the browser to run tests with the current files (including any changes made since last run). Did you mean to have tests run even without a refresh on every change?

— Reply to this email directly or view it on GitHub https://github.com/defunctzombie/zuul/issues/180#issuecomment-87316925.

rase- commented 9 years ago

Thoughts on optional forcing of a re-run, @defunctzombie?

vvo commented 9 years ago

auto-reload of tests with an options would be really useful. A testing flow with auto relaunch of tests is very interesting.

I think @thlorenz did it but in userland.

While we could just leverage http://www.browsersync.io/ programmatic API to do it.

:+1:

andreypopp commented 9 years ago

While we could just leverage http://www.browsersync.io/ programmatic API to do it.

It looks interesting, though I have it implemented through socket.io at the moment in a local branch which just propagates watchify and webpack events to browsers.

But I think we need to change how tests are executed first. It is dangerous to introduce new code into testing environment as it could potentially clash in some way with actual tests. So I think we need to move test execution into an <iframe /> element while keeping reporting code and auto-reloading orchestration in main browser window. I am yet to submit a PR for that.

By the way, what browsers zuul supports?

sublimator commented 7 years ago

bump :) 👍