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 Apr 29, 2024. It is now read-only.
I'm using the capybara-screenshot gem in order to have automatic screenshots when a test fails, but when I run my test suite, using zeus-parallel_tests, and a first test fails, a screenshot is generated, but later, in the case another test fails, the first screenshot is destroyed, and new ones are appearing.
I guess this come from that the fact that there are many processes running (like if they are alone), and as I'm using Capybara::Screenshot.prune_strategy = :keep_last_run, then the folder is destroyed/re-created as soon as a an error occurs.
How could this be addressed in order to prevent this behaviour?
The text was updated successfully, but these errors were encountered:
First of all, thank you for this awesome gem 👍
I'm using the capybara-screenshot gem in order to have automatic screenshots when a test fails, but when I run my test suite, using zeus-parallel_tests, and a first test fails, a screenshot is generated, but later, in the case another test fails, the first screenshot is destroyed, and new ones are appearing.
I guess this come from that the fact that there are many processes running (like if they are alone), and as I'm using
Capybara::Screenshot.prune_strategy = :keep_last_run
, then the folder is destroyed/re-created as soon as a an error occurs.How could this be addressed in order to prevent this behaviour?
The text was updated successfully, but these errors were encountered: