You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 29, 2024. It is now read-only.
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.
The text was updated successfully, but these errors were encountered:
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
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.
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.
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 implementingwebdriverjs-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.The text was updated successfully, but these errors were encountered: