need to call autorun in last spec if using browser about opal-rspec

[elia]

The alternative is to manually call Kernel.exit which in turn would trigger at_exit block which is the trick used by rspec/autorun (also by minitest) if I understood the problem correctly…

[catmando]

None of this was needed in 0.7, it feels like a problem introduced in 0.8

[jgaskins]

Would an Opal.Kernel.$exit() call inside the rendered page somewhere after all the scripts are loaded work?

[catmando]

A call to Opal.Kernel.$exit() after everything is loaded would almost for sure work, but I still say this looks like some kind of regression introduced in 0.8

[jgaskins]

@catmando Certainly, I actually meant to direct that at @elia as a potential solution for opal-rspec, not to go into your app specs. :-)

[wied03]

@catmando, @jgaskins - I agree. This is more of an issue with opal-rails than opal-rspec I think. See discussion in opal/opal-rails#67. The reason I say that is in opal-rspec itself, the autorun call always is done last. It's only in the recent changes to opal-rails (which does its own thing for the browser test runner) that changed.

[wied03]

I'll go ahead and close this due to the PR/issue in opal-rails referenced above.