That makes the specs highly vulnerable, as changing introducing a constant should happen for a reason - to keep the code DRY. It's just the same situation as with typehinting all the collaborators or using `@mixin` - the refactoring in most IDEs will understand it and prevent us from unnecessary, repetitive work.  As for a non-existing constant, it's nothing unusual while writing specs, as you also don't have the SUT or methods you are using on it :) 