@djmitche you caught me :/

I was a bit torn. Yes, this definitely needs tests. And I duplicated the tests for the Parameter and Property. Here is the thought process I went through (maybe not the greatest, but it is what it is):

  * Parameter and Property both have a contract that is directly visible to the end user around what is accepted and what isn't
  * Coercion is used by those two to provide their functionality
  * Coercion is therefore tested to the fullest extent that it currently needs
  * The duplication is not great, but is a result of the split of Parameters from Properties. I could have dealt with that a shared_example, but I'm not too great at those and felt a bit rushed to get the next 3.3.0 RC ready

So I can definitely go for pushing the complete tests for the Parameter and Property to the Coercion module and leave a minimal set for the Parameter and Property.