chainmailguy
Occasional Contributor
Joined 11 years ago
User Profile
User Widgets
Contributions
Re: Remote desktop resolution woes
I ran into something similar. The scripts run as expected when I'm connected via RDP but as soon as I disconnect the desktop size reduces from 1920 X 1280 to 1024 X 768. Image comparisons were failing because the actual image was compressed into a 1024 X 768 space. This on a Win10 X64 machine with TC V14 being accessed remotely. The solution was to go into the Registry and find all instances of 'Screen Resolution' and 'Desktop Resolution' and change them to 1920 X 1280. There were 14. The change seems to have occurred after a recent Win10 auto-update.1.4KViews0likes0CommentsRe: Table Checkpoint - How to ignore numeric differences past the 10th decimal place
Please add my vote for this feaure. Either ? and * wildcards, or Greater Than / Less Than by absolute or percentage for numerics or something similar to the cmpCompare function in the If/Then statement would be sufficient. Can you give me a hint what the custom code might look like? I've found the Compare Properties function but it's kinda painful to set up a separate check step for each cell in a grid.1.6KViews0likes0CommentsPosition Command Offsets 7 Pixels to the Right
Some of the checks I need to perform in TestComplete keyword tests are image comparisons. In order to ensure image comparison consistency between machines I specify the same screen resolution, application window size and position before I begin the rest of my scripts. The command I use is described here: https://support.smartbear.com/testcomplete/docs/reference/test-objects/members/window-and-process/position-action-window-object.html and what I use to push the app to the top left corner of my screen is this: Position 0,0,1300,1050 I noticed a number of my image comparisons were failing and upon closer inspection found that the above command was actually setting my main application window 7 pixels to the right, thus causing image differential comparison failures. The workaround is to use this command: Position -7,0,1300,1050 which actually sets the top left pixel of the main app window to 0,0 Notes: - This seems to have started with the V12.3 release. - Occurs on a physical and virtual machine, with TestComplete and TestExecute. - I also have the patch installed to correct the Auto-wait timeout randomly resetting to 50mS, which is discussed here: https://community.smartbear.com/t5/TestComplete-General-Discussions/TestComplete-Auto-wait-timeout-sets-to-50ms-by-itself/m-p/142185#M26467 The Maximize command does not suffer from this. I choose not to use this command because I like having my app and TestComplete onscreen and non-overlapping for debugging reasons. Has anyone else run into this?640Views0likes0CommentsRe: Incorrect Targets Identified in Record/Playback of Keyword Scripts
It seems the problem *was* resolution-related. When setting screen resolution in Windows there are 3 things I can change: screen resolution, pixel height for groups of items, and a slider for adjusting screen object size. The slider was set to a non-default value, which caused TestComplete to improperly locate items on record and again on playback. Resetting this slider to its default value and restarting the machine fixed the issue.1.8KViews1like2CommentsIncorrect Targets Identified in Record/Playback of Keyword Scripts
Using TestComplete 11.20 with Windows 8.1 I'm finding that keyword tests that are recorded with an XY component are not being correctly targeted as shown in the Test Visualizer after recording or playback. Sometimes the recorded Visualizer images are correct, sometimes not. There seems to be an XY offset applied to the coordinates that is repeatable, but incorrect enough to make the tests click in the wrong place. Specifically the issue occurs when I try to check the checkbox of an Infragistics UltraTree control with the clickItemXY command. May also occur with other XY-related commands but this remains untested. - Issue occurs on VM and physical machine. - Issue occurs with a repeatable XY offset - Issue does not occur with commands that do not use XY coordinates - There are no commands available to me that will check or clear a checkbox without using XY (ie. cbCheckItem does not work with Infragistics controls) - The project will not be modified to us a non-Infragistics control - Changing window size or screen resolution does not affect the issue - Faking out the clickItemXY command by manually calculating in the offset is a non-option. What am I missing?Solved1.8KViews0likes4Comments