Solved
Discrepencies around COM Object registration
Hi, I am currently writing a C# Library to manage Test Execution using the Test Execute COM Object and I have a concern on the COM registeration.
I have both Test Complete and Test Execute installed on my machine, and the documentation here indicates there should be a "TestExecute Library" for Test Execute, i.e.
"Find TestExecute Library (TypeLib Version: 10) in the list of available components and add this library to your project.
Note: TestExecute is based on the TestExecute platform and has the same library name (TestExecute Library). To make certain that you selected the item for TestExecute, check the value of the COM page’s Path column. It should specify the path to TestExecute.exe."
However when I first attempted to add the reference, I only had a "TestComplete Library" for Test Complete.
I then attempted to registere Test Execute using:
"E:\DevApps\SmartBear\TestExecute 10\Bin\TestExecute.exe" /regserver
I now still only have a single "TestComplete Library" which now points to Test Execute having seemingly over written the Test Complete one.
Also, the the rest of the Test Complete Objects now have a mixture of references, some to Test Execute and some to Test Complete, as shown:
Is this expected behaviour?
My concerns are:
1. I never had a "TestExecute Library" available, even though I had Test Execute installed, should I have had?
2. Registering Test Execute has overwritten Test Complete, is this expected?
3. My machine is now in a state that isn't even remotely close to that described in the documentation, is the documentation correct? is there something I need to do to remedy this?
Regards,
Phil Baird
I have both Test Complete and Test Execute installed on my machine, and the documentation here indicates there should be a "TestExecute Library" for Test Execute, i.e.
"Find TestExecute Library (TypeLib Version: 10) in the list of available components and add this library to your project.
Note: TestExecute is based on the TestExecute platform and has the same library name (TestExecute Library). To make certain that you selected the item for TestExecute, check the value of the COM page’s Path column. It should specify the path to TestExecute.exe."
However when I first attempted to add the reference, I only had a "TestComplete Library" for Test Complete.
I then attempted to registere Test Execute using:
"E:\DevApps\SmartBear\TestExecute 10\Bin\TestExecute.exe" /regserver
I now still only have a single "TestComplete Library" which now points to Test Execute having seemingly over written the Test Complete one.
Also, the the rest of the Test Complete Objects now have a mixture of references, some to Test Execute and some to Test Complete, as shown:
Is this expected behaviour?
My concerns are:
1. I never had a "TestExecute Library" available, even though I had Test Execute installed, should I have had?
2. Registering Test Execute has overwritten Test Complete, is this expected?
3. My machine is now in a state that isn't even remotely close to that described in the documentation, is the documentation correct? is there something I need to do to remedy this?
Regards,
Phil Baird
Hi Phil,
There is no TestExecute library. You need to add the TestComplete library which refers to TestExecute, like it's listed in the article.
We will correct the information in our documentation.
