grainwave
Occasional Contributor
Joined 15 years ago
User Profile
User Widgets
Contributions
Line Coverage of Delphi app crashing
When using the coverage profiling, I can test our Delphi app by routine. However changing it to line coverage crashes the app straight away. Also, in Test COmplete when changing a tested apps property to be 'profiled'. I get an error when trying to launch the app stating aqtime was not installed properly. I have re-installed just to be sure but it still gives me the error.10KViews0likes1CommentRe: Remote Log Not Available
Hi Allen, I tried applying the patch and now recieve no results back from the remote machine. Before I was getting a message saying 'remote log not accesible' Now there is no node in the tree for the remote log at all I am using version 7.52.678.7 of TestComplete Further to this I have found that the test is not actually running on the remote machine. However it returns a pass. cheers2.1KViews0likes0CommentsLog Images Mixed Up
Hi, I'm using html format to store my results. However is seems every now and again my logs are getting the screenshots mixed up. This is not a fault of the test script, as it can run once and be correct, then at a later date run and have mixed up images. My test suite is pretty massive so some of the log files get up around the 100MB range. To save the log files i'm using Log.SaveResultsAs('C:\AutomatedTestLogs', 1); Any ideas what could be going on here? cheers12KViews0likes1CommentRemote Log Not Available
When runnning a Test Complete network job I occasionally get a warning in the log 'Remote log not available' and can't see the log generated from the test that ran on the remote machine. However I can log onto that machine and view the log which verifies that the test completed successfully. However from the testExecute command line running on the host I get a return code of 1. I assume this means that the master project has lost communication with the remote machine somehow. Is it possible to verify somehow that this is the case? Perhaps TestExecute should return a special return code if it loses communication with the remote machine?11KViews0likes6CommentsRe: Remote Hosts filesystem mapping to local
Turns out I fixed the issue by changing the VM Network configuration from NAT to bridged. I have a very flaky understanding of how VM's work to say the least but assumed it was a test complete issue since windows managed to map the address to the vms filesystem fine. Sorry for the noob mistake Cheers2.3KViews0likes0CommentsRe: Remote Hosts filesystem mapping to local
Hi David This is not correct. The IP addresses of both machines are different. I can ping each machine from the other and the IP address is resolving correctly as it should. Accessing each machines file shares using the hostname or ip behaves as expected which indicates to me that it is something more specific to the way testcomplete comunicates with tcrea to access the filesystem of the specified host. I will investigate further with Wireshark, perhaps you could give me some more info on what protocol testcomplete uses to communicate this information so I know what packets to be looking at? Cheers2.3KViews0likes0CommentsRemote Hosts filesystem mapping to local
I have a VM running vista, somehow what TestComplete thinks is the filesystem of the VM is actually the Local machine. The problem seems to be intermittent. Restarting the machine does not help. Restarting the VM does not help. Windows maps the files correctly. E.g if I go to \\winvista32sp102 (the vm name) in explorer, it maps to the vm as it should. As a result the test fails to verify, cannot find the project file. Screenshot 1 - shows TestComplete displaying incorrect mapping Screenshot 2 - The Hosts configuration Screenshot 3 - Absolutely no changes made, just time, shows test complete mapping to the correct path. cheers11KViews0likes4Comments