Unit Testing on Windows C ++: Testing a DLL-Exported Class

Question

I have a new native C ++ class that I want to test. It is exported from dll (the project consists of 1 exe and a large number of dll)

Which is better: check it with static binding or by dynamic linking? What do you usually do in your projects?

The problem is that in the project I'm working on, it will take a long time to make it compile statically. So I want to know that testing costs a lot of refactoring.

Thanks in advance

Answer 1

DLL, , ( ).

Answer 2

.

, , . , , "back end".

. , , .

, , , . , / , .