alinder
Contributor
Joined 14 years ago
User Profile
User Widgets
Contributions
Unexpected/overlapping windows aren't being detected
My handlers for OnOverlappingWindow and OnUnexpectedWindow aren't firing in the cases where I really need them during test execution. I've ensured the conditions are not being ignored in the project properties. I've added additional calls to invoke .Activate() on my test objects in case the other methods being used are not appropriate to trigger the check. The windows I need to detect are from the Windows operating system in Windows 8 and later versions. Our office has sufficient Microsoft licensing for all our machines, but aspects of how the machines are maintained and imaged that I can't control make it so that I cannot keep the licenses activated on the machines. Every couple hours a full-screen Activate Windows prompt interrupts our test cycles. I need to establish a workaround such that we can pause test execution until a test proctor can deal with the uncontrollable interrupt screen. Other examples of overlapping windows that are not being detected are the Windows 8 prompts that indicate certain Metro apps cannot be opened when UAC is disabled.1KViews0likes0CommentsRe: ChildCount property value not updating correctly in TestExecute 10
I had first tried RefreshMappingInfo because of the guidance in this thread, and the descriptions imply cached data ought be cleared as the object was mapped to an alias. (TestExecute 10.10 is the version in use, for reference.)1.2KViews0likes0CommentsChildCount property value not updating correctly in TestExecute 10
I have a block of code in a custom script operation that iterates through all the children of a panel and writes their text values (if any) into an array for a specific kind of test. This used ChildCount on the panel to dimension the array, and then as the upper boundary on the loop we use to iterate through the child objects. This code worked without issue in TestExecute 8 and TestExecute 9. However, in TestComplete 10 the ChildCount value is remaining from an older version of the object, and is only being updated when the text value for the child object is being read out inside the loop. This results in test exceptions when the loop tries to perform actions against objects that don't exist. In all versions, Aliases.RefreshMappingInfo was called before retrieving the panel object. During the debug process for this issue, RefreshMappingInfo was called directly on the panel before operations were taken with it, with no improvement. The workaround that has been found to work is calling Refresh on the panel, which seems to be the apparent workaround. It is not ideal that our test code requires modification to execute properly when we test agaisnt Windows 8.1 with TestExecute 10.2.6KViews0likes5CommentsTime-shifting test and TFS source control
Some of my testing involves changing the client PC date. The problem is that whenever a test ends with the client date shifted, I get a series of about 5 or 6 frustrating popup dialogs from the integrated MS Team Foundation Server source control for failures to connect/authenticate with the server. Obviously my tests attempt to restore the correct date when they terminate normally, but this persists as a problem during test development and debugging. Why is TestComplete trying to make this connection at that time? No scripts under control ought be changing due to test execution; are there additional files I need to exclude from control?4.5KViews0likes2CommentsRe: How to validate (x) button exists on a window.
I had a lot of trouble with this as there is no corresponding object to map. I think that it might be possible to verify the Close Button exists by verifying if the window frame has the property ControlBox = True, but that seems to control both the X button and the window menu in the upper left.992Views0likes0CommentsRe: Object Spy objects that are hidden?
I often switch to using the Object Browser if in a deep tree of objects. If the subobjects aren't exposed conveniently for that, I will sometimes just pause at a breakpoint in some dummy code and use Debug -> Evaluate to do the long guess-and-check approach.746Views0likes0Comments