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
I have one question since I'm not an expert in ruby/fastlane. I'm testing some actions and some of my tests are the wrong path where the action should raise a user_error!.
Running them from the Fastfile they work cool! But if I run them from spec it seems to not stop the test.
example:
put_error!("jsons_paths cannot be empty ❌")if[].empty?puts'something else'defself.put_error!(message)UI.user_error!(message)end
something else is being executed, but if I raise an error the test just stop there. Is there a particularly way to handle this situation?
It would be a good practice to add raise StandardError(message) in put_error! method after user_error!?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi! :D
I have one question since I'm not an expert in ruby/fastlane. I'm testing some actions and some of my tests are the wrong path where the action should raise a user_error!.
Running them from the Fastfile they work cool! But if I run them from spec it seems to not stop the test.
example:
something else
is being executed, but if I raise an error the test just stop there. Is there a particularly way to handle this situation?It would be a good practice to add
raise StandardError(message)
in put_error! method afteruser_error!
?Thanks!
Beta Was this translation helpful? Give feedback.
All reactions