User Profile

raz789

Occasional Contributor

Joined 6 years ago

6 Posts3 LikesLikes received1 Solution

View All Badges

User Widgets

Contributions

Re: Color differences in two Operating Systems
Found the fix. Had to edit the highlight rgb in the registry.
6 years ago Place TestComplete Questions
942Views
1like
0Comments
Color differences in two Operating Systems
Hi, In our Testcomplete project we have a lot of region checks that were recorded on a Windows 8.1 machine. Testing on a Windows 10 machine leads to these checks failing due to Color Differences. This can be seen in the following: Left is Win 8.1, Right is Win 10. I've checked the Bit Depth and both PCs are 32-bit color depth. Adding a tolerance to every check in the project isn't an option as there are color differences required in some tests. Is there any way we can solve this? Are these Windows specific settings?
Solved
6 years ago Place TestComplete Questions
945Views
0likes
2Comments
Re: Name mapping does not work with TestExecute in a VM
Hi, This has actually been elevated to a ticket. So it'll hopefully be solved there. I'll mark tristaanogres answer correct. Thanks, Ryan
6 years ago Place TestComplete Questions
2KViews
1like
0Comments
Re: Name mapping does not work with TestExecute in a VM
Ah sorry, I'm still new to this, but I believe you're correct. Looks like one of the mapping properties for the button doesn't exist in the VMs. Not entirely sure why.
6 years ago Place TestComplete Questions
2.1KViews
1like
1Comment
Re: Name mapping does not work with TestExecute in a VM
It's definitely not how the objects themselves are mapped. Using the literal mapped object path works. Aliases do not. The object spy returns the same mapped object path in the recording environment and the VM. The error is simply it can't find the object in the application based on the Alias. The test will just sit and wait for the object. There would be too much code to go through at this point to change it from aliases to the literal path (the one using "Sys.XX").
6 years ago Place TestComplete Questions
2.1KViews
0likes
3Comments
Name mapping does not work with TestExecute in a VM
Hi guys, Currently trying to get TestExecute to run our project on a VM. I'm running into an issue where none of the name mapping Aliases work. The objects can't be found during the test if aliases are used. What does work is using the Mapped Object name. What works (the object spy for the VM reports the same mapping as the PC where the test was recorded): #VM object spy WIN10 Sys.Process("AppTEST").VBObject("frmMainNew").Window("MDIClient", "", 1).VBObject("frmBackGround").VBObject("Picture1").VBObject("frameButtonsMain").VBObject("cmdMaintenance").Click(330, 65) #Test Recording PC object spy Sys.Process("AppTEST").VBObject("frmMainNew").Window("MDIClient", "", 1).VBObject("frmBackGround").VBObject("Picture1").VBObject("frameButtonsMain").VBObject("cmdMaintenance").Click(330, 65) What doesn't work: Aliases.AppTEST.frmMainNew.MDIClient.frmBackGround.Picture1.frameButtonsMain.cmdMaintenance.Click(330, 65) The VM is running 14.0.308.11 The Host PC is running 14.0.308.7 Am I missing something in the settings? Do I need to run TestComplete on the VMs first before TestExecute will work properly?
Solved
6 years ago Place TestComplete Questions
2.2KViews
0likes
7Comments