I'm trying to use TestComplete 7.52 to test a WPF application.Whenever I try to select a control inside of the WPF app window, TC sits and thinks for many minutes and I lose control typically of both TestComplete and my application, usually having to force a close on the WPF program. We had another WPF program that I can test perfectly with TestComplete.I also tried to run some Tests against Microsoft's Blend, which I understand is written in WPF as well. It worked with blend but I noticed it would only identify click locations and not the actual objects or controls.Is this also expected behavior? Is there some sort of add-on I'm missing to test WPF applications? What would cause my program to shut down when being accessed by TestComplete?I appreciate any help with the matter.

Hi Vince,To investigate the problem and find its cause, we need additional information on the issue. To collect this information, please follow the steps below:1. Download the Debugging Tools for Windows package from:http://www.microsoft.com/whdc/devtools/debugging/installx86.mspxand install it.2. When TestComplete hangs, open the "Start | Run..." dialog and execute the following command:"C:\Program Files\Debugging Tools for Windows\windbg.exe" -pn TestComplete.exe -Q -pd -c ".dump /m C:\Dump1.dmp;q"This command will make WinDbg write a memory dump of the TestComplete.exe process to the "C:\TestComplete1.dmp" dump file. After the dump is written, WinDbg will be closed.3. Run a similar command to generate a dump of the tested application:"C:\Program Files\Debugging Tools for Windows\windbg.exe" -pn TheApp.exe -Q -pd -c ".dump /m C:\TheApp1.dmp;q"4. Correct the dump file names in the above commands (for example, change them to TestComplete2.dmp and TheAapp2.dmp), wait for two minutes and execute these commands again.5. Repeat step 4.6. Send us all of the generated dumps via the Contact Support form.

Thanks for the detailed help David.Unfortunately when I tried to run it again, my Application wouldn't hang our crash this time. Some times it'd be a little slow to respond, but only a matter of seconds.It now seems my problem is with TestComplete finding items within the window. Once my mouse enters the applications window, it won't discover any of of the clicks, objects or mouse movements inside.What can you tell me about how TestComplete discovers objects, or why there would be problems from within a WPF application?Thanks.

Hi Vince,Please describe in detail exactly what happens. Do you see individual objects of your application in the Object Browser panel? Can you record actions with individual objects of the application?What can you tell me about how TestComplete discovers objects, or why there would be problems from within a WPF application?There can be a problem if your application does not react in a timely manner to TestComplete's requests. If this is the case, you can try increasing the 'Method invoke timeout' option in your project. To find this option, double-click your project name in the Project Explorer panel, switch to the 'Properties' page and activate the 'Open Applications' options group.

It doesn't time out or crash. I can move around freely while recording a test, the program will respond to button clicks and move. But if I was recording the test, nothing shows up in the steps except for the program launch.On the record dialog that will show object types and names when the mouse moves over them or selects, nothing changes. This is what the object name is for the whole screen:["Window"]("HwndWrapper[ConsoleUI.exe;;31f7e182-0c0d-4cde-8177-29ca597ba177]", "App", 1)

Hey.. Im also involved in testing a WPF application.. I noticed the same issue. When I restarted my machine, I couldnt reproduce the issue. But occasionally this happens. Please post the solution when you find one.. .Thank you.

Testing WPF Program Causes Crash | SmartBear Community

Dmitry_Nikolaev
Staff
15 years ago

Hi Vince,

We have not faced problems with WPF on this OS. I still think that the problem can be caused by .NET Framework 4, which can be installed on your machine. Please send us the information I asked earlier, and I will send you a patch for the .NET Framework 4 problem.
kennedyv
Occasional Contributor
15 years ago
I'm relatively certain .NET 4 is not the issue, but I installed AQtime and tried your steps. When I go to hit start it shows me the error I've attached. During the AQtime install I noticed it complained about no Microsoft Debugger so I went and installed that and it didn't seem to fix my problem.

What do I need to do to fix that?
jenli
Contributor
15 years ago
I do not think this is related to .NET 4 since we have been using .NET 3.5.
jenli
Contributor
15 years ago
Today, the sample WPF orders application was recognized as window application after I started it outside of TestComplete.

I saved the TCObject file. Please see the attached file for your investigation
WPFOrdersRecognizedaAWindow.zip3.3 MB
Madhi
Contributor
15 years ago
I will send mine ASAP

Dmitry_Nikolaev

Staff

15 years ago

Hi,

I'm relatively certain .NET 4 is not the issue, but I installed AQtime and tried your steps. When I go to hit start it shows me the error I've attached.

Is the application mentioned in this dialog a tested application?

A message about script debugger should not cause any problems.

Today, the sample WPF orders application was recognized as window application after I started it outside of TestComplete.

I saved the TCObject file. Please see the attached file for your investigation

Yes, the application is not recognized as Open indeed. Do you have steps for reproducing this behavior reliably?

kennedyv
Occasional Contributor
15 years ago
The 'module' it's complaining about seems to be of no importance to the .exe I'm trying to launch.

I can't start AQtime so I can't follow your steps further.
jenli
Contributor
15 years ago
Hi David,

The WPF orders application coming with TestComplete is an open application itself. The issue is TestComplete sometimes can not recognize it as an open application. It is impossible to reliably reproduce it because this issue occurs only sometimes with the same steps. I will say about 90% of time our tested open WPF application is recognized as an open application.

You perhaps should look at in what situation TestComplete treats an Open application as "Black Box" application.

This is a serious issue for us since our nightly smoke testing sometimes can be failed right away without running real tests yet.

Dmitry_Nikolaev

Staff

15 years ago

Hi,

The 'module' it's complaining about seems to be of no importance to the .exe I'm trying to launch.

Do you have this module added to the Setup panel? If you do not have this module, could you please try reinstalling AQtime?

You perhaps should look at in what situation TestComplete treats an Open application as "Black Box" application. This is a serious issue for us since our nightly smoke testing sometimes can be failed right away without running real tests yet.

We agree that this is a problem. However, it does not occur on our computers, and we need to investigate it to be able to find its cause. Please send us the AQtime log as I requested.

kennedyv
Occasional Contributor
15 years ago
I'm not sure what you mean.

I was following your instructions and I got an error. I don't know how to add a module to the setup panel.

I'll try reinstalling AQtime.

Forum Discussion

Testing WPF Program Causes Crash

Related Content

Java.io.IOException - Cannot run program "C:\Program": CreateProcess error=2

Testing program on Delphi

Long delay causes test to hang

Caused by: groovy.lang.MissingPropertyException: No such property: testCase for class: Script2

Resource profiler causing program being tested to crash

Recent Discussions

Login for Zephyr is through Microsoft 365 and TestComplete can't complete login

Is it possible to add Device Info from a remote browser to the Log Folder?

Support for Windows Server 2022

Count number of test cases in Execution Plan

How to stop TestComplete from failing a test when unrelated processes crash?