I just discovered I get no errors if there is no mapping to a property if the source has a property with the same name. We are trying to make it as strict as possible and get errors when there are unmapped properties. It seems like Assert.IsConfigurationValid() doesn't do that. Is there a way to make it work with stricter control?
I dont believe that there is. I had a similar problem on a recent project.
What we did was ensure that every property on the target was specified in the mapping configuration in alphabetical order. Even if it was being ignored.
When errors occured it was possible to do a "visual" check of the target to see if any properties had been added / missed.