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
The idea being that for some scenarios we do not all the variables to be used. (e.g., a method which has several guard clauses which each check one or more inputs).
But this does not clearly communicate that the inputs should not actually be used in the first 2 examples. It makes it hard to see which examples expect an actual nil.
The variable with the :no_op value could make use of the memoizing/let blocks in order to raise an assertion if the variable is called during the scenario. But that might be unnecessarily complex.
The text was updated successfully, but these errors were encountered:
The idea being that for some scenarios we do not all the variables to be used. (e.g., a method which has several guard clauses which each check one or more inputs).
Given a method like this:
I might have a tabular spec like this:
But this does not clearly communicate that the inputs should not actually be used in the first 2 examples. It makes it hard to see which examples expect an actual nil.
So I would like to have:
The variable with the :no_op value could make use of the memoizing/let blocks in order to raise an assertion if the variable is called during the scenario. But that might be unnecessarily complex.
The text was updated successfully, but these errors were encountered: