I am testing a WPF application that needs to open after services are started. I have written another application that starts the services and then the WPF application (application under test) and I used this launcher as my startup application. The problem is, that my tests fail because the WPF MainWindow window is yet available. Does this WPF MainWindow need to be a child of the startup application? Is there a way to make the test application wait for the MainWindow to launch?
The reason why I am doing it this way, is that I need to restart the services and application after each test, and not just the wpf test. Any suggestions?
2 Answers, 1 is accepted
Hi Terry,
This is somewhat common scenario, although for different reasons, but I think you will find this approach suitable for you. As the test starts, Test Studio will launch the application that is configured for that WPF test. If you need to connect the execution to another WPF application, you can use the suggestion in this article. The example shows how to connect to a running application based on the process name, but you can use other process properties.
Once the test is done, Test Studio will close the application it was connected to. I would like to point out that you need to ensure that the application is in the expected state, before it is closed. This might affect the state of the application when it is started again next time.
Let me know if the suggestion does not cover your scenario and share more details. I will be happy to continue our discussion and assist you.
Regards,
Plamen Mitrev
Progress Telerik
Does UI testing really fit into CI/CD?
If you want to find out how to take advantage of continuous delivery pipelines, join our Test Studio webinar on Wednesday, April 6 at 11 am EST | 5 pm CET.
Rank 1
Iron
ActiveApplication.WaitForWindow(string caption, int timeout);