Not sure this is a bug or
I am trying to test class the creates a COM object. I
use MFCTestRunner for testing.
I found that at the first the COM object wouldn't load
because CoInitialize was corrupted by the testframe work.
I had CoInitialize in the main application prior to
In that case the class under test, failed to load the
COM object. Placing the CoInitialize in the setUp
function of my test class, allowed loaded the com object.
However, the QueryInterface on the object still fails.
It seems that the test framework is disrupting some the
com loading/handling capabilities of windows.
PS: The COM object works flawlessly outside the test