> In this case, it seems like it's appropriate to not to catch the exception from the object under test and break composability?

> I think I'll need to refactor to test for responds_to?.

Leveraging `respond_to?` sounds good, and then if the object still raises `NameError` when the predicate is called letting that propagate up (since it's essentially a broken object, apparently) is good.

Just be sure that objects that do not respond to the predicate do not trigger exceptions, please.