TestComplete and WPF
I've a .net 8 WPF project where I have the following steps to build it: Compile the app use donet publish Create an msi When I compile and run the app TestComplete recognizes my app as a WP...
Forum Discussion
Thanks for your reply Marsha!
I think your first link got me to another link that identifies the possible problem:
https://support.smartbear.com/testcomplete/docs/app-testing/desktop/net/supported-technologies.html
There is a bullet point that says:
- You should compile the tested application with the self-contained single file option set to false for TestComplete to work properly during local testing.
the dotnet publish command does create a self-contained version of our application. It is a product requirement that we bundle this way and install this way. My question is WHY does testcomplete require us to stay away from self-contained.
We build our installer and hand it to the automation engineer that is using test complete. And our eventual target install environment will require this approach
Thanks for any insight
I understand your requirements. What my teams have done in the past is to give the bundle to whoever is testing, let them install it manually, and then proceed with TestComplete tests. It really doesn't add any information to have TestComplete retest the install each time you want to repeat a product test.
As to why the TestComplete requirement is that way, you'll need to ask Support that question. Here's the link to contact them.
https://support.smartbear.com/testcomplete/message/
