Retries per file #1
Conversation
Previously only test-level and suite-level retries were available, which are fine in most cases. In any test which involves state, such as on a server or in a db, the state may be left invalid once the test fails the first time. Any subsequent retries may have no chance of passing due to the invalid state they would have to start with. A new browser instance is created for each specfile, which makes this an ideal place to hook and setup any other states (server, db). Retries on this level would mean that the whole setup process could simply be repeated as if it were for a new specfile, with the results of the failing specfile (that is to be retried) being discarded.
This allows the reporter to set the start and end properties of runnables to the time the event happened as opposed to the time the reporter got notified of the event.
|
|
|
@christian-bromann should unit tests be launched automatically for this PR? |
|
Close\reopen to trigger CI |
|
@BorisOsipov Could you please check credentials on CI? |
|
@shackijj unfortunately, tests won't work on Travis. I disabled them. See #6 (comment) |
|
@christian-bromann @BorisOsipov |
|
Given the situation that this PR isnt' merging to boneyard master soon, I need to use this feature by make my own package... QUESTION: If I fork and do npm package, anything/steps I need to modify/add to make it work in order to have it work the same as webdriverio out of box(simply just npm install solving the problem)? What I tried, pack this and remove the previous webdriverio and install the newly made package. It throws message as : |
Proposed changes
This PR resolves #2484.
I took commits from PR 2930 which was closed due to migration v4 to a separate repository.
Types of changes
Checklist
Further comments
Reviewers: @christian-bromann