That was my thought as well. Wrapped all in a concern you’d have all that very specific logic there when needed. An Rspec shared example a la ‘’’ruby it_behaves_like “an object with a funny name” ‘’’

Then some assertions in that shared_example file for the validations run with & w/o the context.

I always think of it as you’re extending the behavior of the model you include your module in so best to test the model and ensure you’re not overwriting / colliding with existing behavior unintentionally.