Jasmine 2.0 Html Reporter: Rerun a failed spec without waiting for all to complete?

[Michael Lehenbauer]

Greetings,

Jasmine 1.3 gave me results as the tests ran, so as soon as any started failing I could just click on one to run it in isolation, and then I could immediately see the issue and debug/fix it.  But with Jasmine 2.0, it doesn't give me any details on test failures or let me re-run a failure until the entire suite has finished running.

This is really messing up my workflow, since my test suite is ~500 tests.  They take about 30s to run normally, but many are async tests and if I introduce certain kinds of bugs, they'll hit their timeout instead of failing quickly, meaning it could take several minutes for the suite to finish running.

Am I missing something?  Is there an easy workaround or a way to get the old html reporter behavior back?

I can try to come up with a PR if there's a specific behavior you'd be willing to accept (I think I basically want the 1.3 behavior back, but I assume it was changed for a reason).

Thank you kindly!

-Michael

[Andrés Muñoz]

Hello Michael,

Awesome changes has jasmine 2.0, one of all that changes is that, an enhacement in testing asynchronous methods without setTimeout.

You can see the api:

http://jasmine.github.io/2.0/introduction.html#section-Asynchronous_Support

kinds regards,

--
You received this message because you are subscribed to the Google Groups "Jasmine" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jasmine-js+...@googlegroups.com.
To post to this group, send email to jasmi...@googlegroups.com.
Visit this group at http://groups.google.com/group/jasmine-js.
For more options, visit https://groups.google.com/d/optout.

--

Andrés Muñoz.

[Gregg Van Hove]

The HtmlReporter was changed primarily for speed. Having it render the full failure right away caused a lot of reflow for the browser which then could actually impact suite run time for large enough suite.

This seems like it might be a good use case for a custom reporter if it's breaking your workflow.

-Gregg

[Michael Lehenbauer]

Thanks guys, 

I'm aware of the new syntax for writing async tests.  That's one of the reasons I upgraded to 2.0.  But it does nothing to help with this problem. :-/

I'm surprised nobody else has run into this, but I guess I'll look into hacking together my own reporter for now.

Thanks,

-Michael

On Thursday, October 2, 2014 4:26:50 PM UTC-7, Gregg Van Hove wrote:

The HtmlReporter was changed primarily for speed. Having it render the full failure right away caused a lot of reflow for the browser which then could actually impact suite run time for large enough suite.

This seems like it might be a good use case for a custom reporter if it's breaking your workflow.

-Gregg

On Thursday, October 2, 2014, Andrés Muñoz <andr...@gmail.com> wrote:

Hello Michael,

Awesome changes has jasmine 2.0, one of all that changes is that, an enhacement in testing asynchronous methods without setTimeout.

You can see the api:

http://jasmine.github.io/2.0/introduction.html#section-Asynchronous_Support

kinds regards,

2014-10-02 16:12 GMT-05:00 Michael Lehenbauer <mic...@firebase.com>:

Greetings,

Jasmine 1.3 gave me results as the tests ran, so as soon as any started failing I could just click on one to run it in isolation, and then I could immediately see the issue and debug/fix it.  But with Jasmine 2.0, it doesn't give me any details on test failures or let me re-run a failure until the entire suite has finished running.

This is really messing up my workflow, since my test suite is ~500 tests.  They take about 30s to run normally, but many are async tests and if I introduce certain kinds of bugs, they'll hit their timeout instead of failing quickly, meaning it could take several minutes for the suite to finish running.

Am I missing something?  Is there an easy workaround or a way to get the old html reporter behavior back?

I can try to come up with a PR if there's a specific behavior you'd be willing to accept (I think I basically want the 1.3 behavior back, but I assume it was changed for a reason).

Thank you kindly!

-Michael

--
You received this message because you are subscribed to the Google Groups "Jasmine" group.

To unsubscribe from this group and stop receiving emails from it, send an email to jasmine-js+unsubscribe@googlegroups.com.

To post to this group, send email to jasmi...@googlegroups.com.
Visit this group at http://groups.google.com/group/jasmine-js.
For more options, visit https://groups.google.com/d/optout.

--

Andrés Muñoz.

--
You received this message because you are subscribed to the Google Groups "Jasmine" group.

To unsubscribe from this group and stop receiving emails from it, send an email to jasmine-js+unsubscribe@googlegroups.com.