[WIP] : Extending workflow to save artifacts for debugging #6101
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Nice, I'm glad that you're taking this on. It will be really useful. |
Thank you, and I apologize for the delay—I had a power outage. :) I’m currently experimenting on this branch and intentionally making breaking changes to gather detailed information about the failures. . |
…fter a form is filled
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What this PR does
This PR extends the CI workflow by adding functionality to save screenshots of failed Capybara tests as artifacts. When Capybara tests fail during execution, screenshots of the failed state are automatically captured. These screenshots will be archived and uploaded as artifacts in the CI pipeline, making it easier to debug and investigate test failures