tomi1187
12 years agoNew Contributor
Unrecognized .net objects
Hello!
I've been searching around the net for quite a while with this issue we are facing sometimes but so far had no luck in finding an answer.
We have an application that uses both WinForms and WPF objects, and TestComplete sometimes fails to recognize them as expected, namely .NET objects. This problem affects both TC9 and TC10, although this issue happened consistently only with the latter. Usually everything works fine, but when this problem happens it causes many of our test cases to fail due to not being able to find .NET properties that I use during test runs.
I saw people complaining about this with earlier versions of TestComplete, there were suggestions there to increase method invoke timeout, which we did, and although it slowed down test runs considerably, it seemed to have solved our problems - until TC10 at least, but today it happened again with TC9.
I saw this article, which I feel might be related: http://support.smartbear.com/viewarticle/9018/
Could there be similar issues with current .NET version and TC9-10 ? I'm only guessing here, it should not be a problem because there are different versions on the test system and my computer for example, and our application is compiled with 4.0 I think.. but still, since I have no idea why sometimes this could happen I'm suspicious of this as well.
Has anyone faced similar behaviour earlier? Perhaps with an explanation on why this happens and what could solve it? :)
I've been searching around the net for quite a while with this issue we are facing sometimes but so far had no luck in finding an answer.
We have an application that uses both WinForms and WPF objects, and TestComplete sometimes fails to recognize them as expected, namely .NET objects. This problem affects both TC9 and TC10, although this issue happened consistently only with the latter. Usually everything works fine, but when this problem happens it causes many of our test cases to fail due to not being able to find .NET properties that I use during test runs.
I saw people complaining about this with earlier versions of TestComplete, there were suggestions there to increase method invoke timeout, which we did, and although it slowed down test runs considerably, it seemed to have solved our problems - until TC10 at least, but today it happened again with TC9.
I saw this article, which I feel might be related: http://support.smartbear.com/viewarticle/9018/
Could there be similar issues with current .NET version and TC9-10 ? I'm only guessing here, it should not be a problem because there are different versions on the test system and my computer for example, and our application is compiled with 4.0 I think.. but still, since I have no idea why sometimes this could happen I'm suspicious of this as well.
Has anyone faced similar behaviour earlier? Perhaps with an explanation on why this happens and what could solve it? :)