Replies: 2 comments
-
One of the main reasons I use Mapperly is the fact that I do not need to write unit test for the mappings. Mapperly does evaluate every property to ensure I have not forgotten any properties. When adding new property to source or target or renaming a property causing a mapping to be missed, I will get an error/warning (depending on my setting). If I have any special mapping used by Mapperly, I do unit tests those methods. But that's outside Mapperly. |
Beta Was this translation helpful? Give feedback.
-
What do you mean with "even if I mock Mapperly too"? |
Beta Was this translation helpful? Give feedback.
-
I have created a mapper class in a separate file as mentioned here. And I've used it in another class for mapping. However, when I'm testing my other class using Moq, I am getting an error saying that it is Non-Overridable even if I Mock mapperly too. What's the best way to unit-test mapperly?
Beta Was this translation helpful? Give feedback.
All reactions