running inside AQTime vs attaching to running process
We are a group of develoipers, working on the same product with the same development tools and the same build process. We run our Unit Test executable in AQTime to compute code coverage. But something strange is happening to a few of the developers: they can only get the results if they attach AQTime to the running process (executable of Unit Tests). If they try to start the run from inside AQTime, it exits almost immediately and does not return any coverage results. There is a pause point at the beginning of our UT executable, and that point is not even reached when running from inside AQTime. For the rest of developers, including myself, AQTime works fine whether we start the run from inside AQTime or attach it to the running process. Since, as I said, our development environments, permissions, etc... are theoretically identical, does anybody know what could cause this very annoying discrepancy?
Note: Support guys may ask you for the problematic binary. If you think that it contains some really sensitive information, it is possible to discuss NDA signing with Support.
Regards, Alex [Community Expert Group] ____ [Community Expert Group] members are not employed by SmartBear Software but are just volunteers who have some experience with the tools by SmartBear Software and a desire to help others. Postings made by [Community Expert Group] members may differ from the official policies of SmartBear Software and should be treated as the own private opinion of their authors and under no circumstances as an official answer from SmartBear Software. [Community Expert Group] signature is used with permission by SmartBear Software. http://smartbear.com/forums/f83/t86934/community-experts/ ================================