New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use the new UI.test_failure! in screengrab #8736
Conversation
Use the new UI.test_failure! in screengrab to handle test failures to get the better success/ failure semantics introduced in #8631
UI.user_error!("Tests failed", show_github_issues: false) if test_output.include?("FAILURES!!!") | ||
else | ||
UI.error("Tests failed") if test_output.include?("FAILURES!!!") | ||
if test_output.include?("FAILURES!!!") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is that for real? 😮
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
YES!!! 😉
Hey @mfurtak 👋 Thank you for your contribution to fastlane and congrats on getting this pull request merged 🎉 Please let us know if this change requires an immediate release by adding a comment here 👍 |
Congratulations! 🎉 This was released as part of fastlane 2.25.0 🚀 |
Checklist
bundle exec rspec
from the root directory to see all new and existing tests passbundle exec rubocop -a
to ensure the code style is validDescription
Use the new
UI.test_failure!
in screengrab to handle test failuresMotivation and Context
To get the better success/failure semantics introduced in #8631