If you really want to, you can use allowing(dependency)
which will allow everything on the object.
There is a reason that we don't support "nice" mocks, which is that we don't want stuff happening arbitrarily in our code without driving it from the unit test. On the whole, we find that this sort of brittleness comes from weakness in our design, and we use the test feedback to help us discover that.
In this example, I would be interested in the relationship, the "protocol" between the different dependency methods. I would want to isolate that so that it's implemented once, which means I would only need to test it in once place, so a "nice" mock would not be as useful.