Hi, I am running into an issue while automating TestExecute using COM Interop. I have created a C# class to run script routines through COM. As each test runs, the memory usage displayed for TestExecute in the Windows Task Manager continues to grow until the entire test run gets brought to its knees.
I am not an expert at COM and may be doing something incorrectly. Here is how I have it set up:
When the class is first initialized, I execute this routine to open the project suite:
The idea here is to only open the project suite once, at the beginning of the test run. This works fine and opens the project suite as expected (and returns a boolean value indicating success/failure in opening the project). Now for each test I run this method:
Just a hint, double posting both here and on the TC forums at SmartBear's site will probably not get you any different or better set of answers. SmartBear's staff monitors both places equally so you'll get the answer in one place and then get referred to it in the other.
Ahh thanks Robert. I was just assuming different people went to the two different forums and I'm kind of in a pinch until I get this fixed... (It's my workaround for the TFS integration issue I posted awhile back.)