Failure Screenshots Dir #5
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
Ultimately, I just want to able to both use
rails tmp:clearto delete local capybara artifacts & also have them accessible to me via download when CI fails. We could accomplish this a number of ways, so feel to propose another if you prefer.Why
While recent versions of Capybara seem to use tmp/capybara as the directory where they store screenshots, the Rails
tmp:clearcommand will not clear this directory. For that reason, I prefer to configure capybara to save failure screenshots into the traditional directory which rails expects:Changes
failure-screenshot-dirwith default value set totmp/capybaraScreenshots