We have been running into an issue where we are running our interactive Coded UI tests, and when our second test starts, the QTAgent32.exe stops working. Our setup is through TFS where we queue a new build that tells a controller to run our tests on VMs. These tests are directly sent to the VMs designated by a .testsettings file. Once the tests are distributed on the VMs, the tests start to work on the WPF application under test. A test can mainly take an hour to run due to the complexity of what needs to be tested. After the test completes and the agent shows '1/10 Completed' we get a windows message that QTAgent32.exe has stopped working.
- Problem Event Name: BEX
- Application Name: QTAgent32_40.exe
- Application Version: 12.0.21005.1
- Fault Module Name: StackHash_83e2
- Fault Model Version: 0.0.0.0
If we close out the Windows message, another will pop up with different details.
- Problem Event Name: APPCRASH
- Application Name: QTAgent32_40.exe
- Application Version: 12.0.21005.1
- Fault Module Name: msxml6.dll
- Fault Model Version: 6.30.7601.18431
If we close the second message, the test will be claimed as complete with a failure in the test results. We also see that the Agent will continue running the next test until it fails on the fourth test!
We have looked at event viewer on both the controller and agents. The controller shows nothing. The agent shows failures with the same details as the errors above. We have repaired the agent and looked into .Net. We know that we can run these tests in any order and that they do all pass without this issue when ran locally. The errors described above are only when ran on our VMs/Agents.
Anyone have ideas on how to either get more details during the test runs? Has anyone else ran into an issue like this before?
Thank you all in advance for taking a look and helping out!
