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
It appears UnhandledHTTPRequestError is a descendant class of StandardError, which means its very easy/likely that, when doing controller/feature specs, this error will get rescued and wrapped in some other client-facing error, which obscures the original VCR error and makes it hard to track down what went wrong.
Does anyone else run into this? Is there a better way to make VCR errors surface to the top without some intermediary rescue getting in the way? It's almost tempting to want VCR errors to extend from some subclass of Standard/Runtime error that most rescue blocks won't catch.
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
-
It appears
UnhandledHTTPRequestError
is a descendant class ofStandardError
, which means its very easy/likely that, when doing controller/feature specs, this error will get rescued and wrapped in some other client-facing error, which obscures the original VCR error and makes it hard to track down what went wrong.Does anyone else run into this? Is there a better way to make VCR errors surface to the top without some intermediary rescue getting in the way? It's almost tempting to want VCR errors to extend from some subclass of Standard/Runtime error that most rescue blocks won't catch.
Beta Was this translation helpful? Give feedback.
All reactions