https://bugs.winehq.org/show_bug.cgi?id=56136
--- Comment #6 from Henrik Karlsson hkarlsson@gmail.com --- I would write code that can traverse through all dlls in system32 and make sure that works.
Then try to write some custom dlls that covers the various cases. I have no idea which parts of the dlls that trigger what behavior though.. When I was messing around with this it really felt very arbitrary, so I think this would be quite hard.
Even though it would be great to have full unit test coverage I think it is more important to just make it work with the dlls in system32 folder once. It is a tricky domain to make unit tests without copying binary data from windows.