Skip to content
This repository has been archived by the owner on Jul 29, 2024. It is now read-only.

When a spec / test fails / fatals, should give the option to retry via parameter #1392

Closed
theogravity opened this issue Oct 1, 2014 · 3 comments

Comments

@theogravity
Copy link

Hi,

I'm aware that webdriverjs-retry exists to retest functions but overall would like to have the ability to retest a spec or a failing test block (spec is more realistic IMO) when it fails instead of implementing webdriverjs-retry for a bunch of functions. We sometimes have tests that are like schrodinger's cat - it sometimes passes and sometimes fails (or fatals). It would be nice to retry the spec rather than rerun the entire conf again because of that.

@theogravity theogravity changed the title When a spec / test fails, should give the option to retry via parameter When a spec / test fails / fatals, should give the option to retry via parameter Oct 1, 2014
@juliemr
Copy link
Member

juliemr commented Oct 1, 2014

I think this is a duplicate of #1190. I think it's a neat idea but It would require a lot of infrastructure that currently isn't available (Protractor has no way to know anything about the prior test run at the moment - we'd have to have a way of storing the previous output somewhere, re-parsing it, figure out how to get the test runner to run a subset of tests (which is tricky for Jasmine)).

The way I do this is just use iit for the tests I want to re-run.

@theogravity
Copy link
Author

Yeah, def is a dupe. Overall we wouldn't want to convert each it to iit, but rather just have the runner detect/retry automatically. Someone also told me that it probably would involve reading result output files, and I understand that can get tricky as there are at least two primary formats people use - xunit and tap and would require infrastructure to appropriately parse for errors.

@juliemr
Copy link
Member

juliemr commented Oct 1, 2014

OK, closing as dupe to continue discussion on the other issue. Thanks for the input!

@juliemr juliemr closed this as completed Oct 1, 2014
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants