Contributions
Re: Splitting up my exported logs
I too have need for this feature, and I am upset to learn that it is not possible in the current version. It seems like the easiest way to provide this is to allow the log to be cleared from scripts. Then I can run a group of tests, export log results, clear the log and then run the next group of tests and repeat. Right now we have the same problem where logs are extremely slow to view (MHT) outside of TestComplete. I am considering the idea of writing a custom tool to drive TestExecute so that I can get separate logs. At any rate, please add me to this request.1KViews0likes0CommentsRe: Using path variables for Tested Apps
When you say path variable, do you mean the Windows environment variable PATH? Or do you mean the column in the Tested App panel called "File Path"? Either way I can tell you what we do. Our AUT is in the Windows PATH, so it is possible to run it without specify a fully qualified path to the EXE. We add the File Name to the TestedApp and leave the File Path value empty. It does not matter where our AUT is installed; the TestApp can be started. If you need to specify the File Path value and your TestedApp might not always be in the same location, I am fairly sure you can update the File Path value from script code at runtime.1.2KViews0likes0CommentsRe: Error viewing locals or inspecting an array of objects during debug
I uninstalled TC 7.5. I also had a version of TC 6 on my system, that I no longer use. I uninstalled it too. I also uninstalled MS Script Debugger. I then reinstalled MS Script Debugger followed by TC 7.5. Problem Solved! A side benefit is that debugging (stepping line by line) is much faster now too. It used to take a few seconds (at least) to wait for control to return to the debugger when stepping over even the most basic line of code.3KViews0likes0CommentsRe: Error viewing locals or inspecting an array of objects during debug
Not sure...your image is coming up blank in my browser. I can only assume that you are offering visual proof that either the problem does not happen for you or that you are now seeing the same issue as me. I have a co-worker who also has problems inspecting objects in debug mode on his install of TC 7.5. However, I just tried installing TC 7.5 on a clean virtual machine, and the problem does not happen. So the problem is seen in certain environments. Perhaps it is related to numerous upgrades of TC (going back to version 5) on my primary work machine? I am going to try uninstalling everything and reinstalling. Maybe this will fix the issue.3KViews0likes0CommentsRe: Error viewing locals or inspecting an array of objects during debug
Thanks for trying, but I don't think you are doing the same thing as me. I am talking about the Locals panel/window that is displayed (along with the Call Stack, Watch List and Breakpoints). If you set the breakpoint where I stated (on the Log line) and look at the Locals window, you should see the error I am talking about when you click the + sign to expand the variable "a". The error actually shows in the Value column for index [0]. The same error can also be seen if you highlight the variable "a" in the code window, right click, and select Debug -> Evaluate. This brings up the Evaluate dialog for expression "a". If you then click Inspect, the Inspect dialog appears. The Inspect dialog shows that for array index [0] the value is "Error: Could not convert..." (same error as I mentioned). I guess I should have stated explicitly that the problem is with debug mode and the Locals window. The problem does not impact the actual use of custom objects inside arrays. These work fine, and (as you said) the expression "a[0].name" does log correctly and can be explicitly evaluated.3KViews0likes0CommentsError viewing locals or inspecting an array of objects during debug
Using the code included below, set a breakpoint on the "Log.Message" line in function "bar". Run "bar". View the Locals window and expand array "a". The value for the first item will be: "Error: Could not convert variant of type (OleStr) into type (Dispatch)" Notice that you can correctly inspect the custom object in variable "b"...just not when it is included as an item in an array.Version of TC is 7.5. function foo() { this.name = "myname"; } function bar() { var a = new Array(1); var b = new foo(); a[0] = b; Log.Message(a[0].name); }17KViews0likes8CommentsRe: aqFileSystem.CopyFile displays message box instead of just returning FALSE
All text from the screen shot is in my original message (title, message, button text) and permissions are not the problem. After more investigation on my part, it appears the problem happens on Windows Server 2003 and does NOT happen on Windows XP. Here is the script: function foo() { aqFileSystem.CopyFile("c:\\doesnotexist\\test.txt", "c:\\test.txt"); } Run this, and the message box will appear on Windows Server 2003.3.4KViews0likes0Comments