Where should the DTO -> Entity conversion methods be and vice versa?

Question

Java

I placed methods in services. Convenient, but there was a problem during testing. The DTO conversion method is called in almost every service method. And now, when testing, I have to check each time if the result matches the desired one, instead of just verify whether the method was called and that's it ( verify cannot be called not on a mock).
There was an idea to transfer the method to a separate class, but I am weak in good practices.
Tell me, please, where would it be correct to transfer these conversion methods?
Should I create a separate mapper package with classes in it? Let's say the EmployeeMapper class has two methods toEmployee, toEmployeeDTO? Am I thinking right?

PS maptract can't use

Answer 1

Should I create a separate mapper package with classes in it? Let's say the EmployeeMapper class has two methods toEmployee, toEmployeeDTO? Am I thinking right?

Yes.
You can go on and on about why this is so, but I don't really see the point.

Answer 2

In a MagicDTO service encapsulating a ModelMapper . For examples here . And forget all these toEntity, toDTO like a bad dream.