Mapping documentatie

[JVerbruggen]

• [x] Strategy pattern benoemen
• [x] Complex input output example
• [x] UML diagram toevoegen strategy pattern (seq & class)
• [x] Write down that they are examples
• [x] Mapping coverage - hoe aanpakken?
• [x] Mapping tests schrijven

[JVerbruggen]

[JVerbruggen]

[JVerbruggen]

@sixdiamants Je had het er laatst over dat je een voorbeeld wilde zien voor de complexe input en output. Wat denk je dat ik nog moet aanvullen op de omschrijving van deze input en output? Ik zie zelf niet echt wat er mist. (https://github.com/JVerbruggen/IMSpoorToEulynx/wiki/Creating-new-mappings)

[JVerbruggen]

Mapping coverage

Is there a way for monitoring mapping coverage, so that not one possible mapping is missed?

I think this is very hard to do because mapping is not simply 1 to 1 in all cases. Often multiple variables are used to construct a certain object. So simply testing whether every variable has been edited in the code, is not a solution.

You can write a unit test for every possible combination of variables, where different mappings are expected, which is a viable solution. But as both models evolve, these will have to be updated along with the mappings.

Another way to test the integrity of mapping is to write algorithms for both ends, checking if the behaviour is the same. This would be rather complex and time-intensive, so it might not be the best solution.