Pinpointing the problem areas of a message mapping can often be a cumbersome job, particularly when dealing with a large mapping. This blog describes a method for evaluating a mapping program based on a set of predefined rules.
The result of this evaluation is a list of areas in the mapping program, that could potentially cause problems. The list can be a good starting point for unit testing (for instance using Detroubulator: Call for beta testers, which will be released in a month or so) or for verifying the mapping in other ways.
