pvidal
Contributor
Joined 16 years ago
User Profile
User Widgets
Contributions
Re: TestComplete triggers exceptions in the tested application.
Hello Jono, I don't have the details because it was a remote team. What I was told is that they had some bussiness logic in the UI code and that the threads were interfering with each other. I never understood why it will fail only with TC and never with user interaction. They separated the bussiness logic from the UI and the problem went away. Regards, Patricio.1.3KViews0likes0Comments- 1.4KViews0likes0Comments
Re: TestComplete triggers exceptions in the tested application.
Hello Alex, The developers did some changes in the threading-UI code of the application and now the tests are executing with no exceptions or hangs. I will keep an eye on the issue and will capture the dumps if the problem comes back. Thank you, Patricio.1.3KViews0likes0CommentsRe: TestComplete triggers exceptions in the tested application.
Hello Alex, 1. We are using TC 7.52. 2. No, the .NET Framework 4 is not installed in any of the machines (all the machines, including VMs, have the same problem). I will follow the procedure to generate the dumps. Thank you, Patricio.1.3KViews0likes0CommentsRe: Split TextObjects
Hello David, I was able to replicate the problem using a simple vbs message box. MessageBox.png shows the vbs dialog with the "Text1/Text2" text. SP2.png shows the log when running in Windows XP Service Pack 2: only 1 TextObject is returned with the "Text1/Text2" text. SP3.png shows the log when running in Windows XP Service Pack 2: 5 TextObjects are returned: "2", Text", "/", "1", and "Text". TestObjectsTest.zip contains the TestComplete project with the code and the logs of the two runs. Regards, Patricio.2.1KViews0likes0CommentsTestComplete triggers exceptions in the tested application.
Hello, Since the beginning of our automation effort on few occasions TestComplete would hang and our application would throw a system exception when TestComplete called WaitWinFormsObject. Because it only happened few times we chose to ignore it and we just re-started the test (these are several hour-long tests). We have kept adding test cases to our projects and now we have the situation where for some of our tests TestComplete will always hang and our application would throw a system exception (I don't know what happens first). So far we these exceptions (always the same on a specific test case): System.Runtime.InteropServices.SEHException at System.Windows.Forms.UnsafeNativeMethods.PeekMessage(...) System.Runtime.InteropServices.SEHException at CWinThread.PreTranslateMessage(...) The exceptions are only thrown when TestComplete is driving our application. They never happen when manually driving our application. TestComplete hangs and it only responds when we kill our application process. We are really stuck on this and I have no clue what to do. I was able to prevent one of the crashes by avoiding the call to WaitWinFormsObject and just doing a delay and a blind click using Sys.Desktop.MouseDown and Sys.Desktop.MouseUp. But I can't use this work around when I need the Window object. The weird thing is that for the test case with the work around the test case continues executing and can call WaitWinFormsObject on other windows. Thank you for your help. Regards, Patricio.18KViews0likes6Comments