ContributionsMost RecentMost LikesSolutionsRe: Problem with global constants and case statement ok i found the issue : in one of my scripts, i'm calling a function with 2 parameters having both default value, like myfunc(); ... but using it with parenthesis breaks everything... must call it myfunc; it should not be the case... Re: Problem with global constants and case statement Hi, I'm facing the exact same issue... with scripts existing and running since a long time... I don't understand what happened, it just suddenly stopped to work, using TestComplete 12 What shall i do?? Thanks Re: Missing Objects/NameMapping/Function(Function Reference) should show in TC Ravik I agree with you, and this feature is a must have in a good IDE. I got so many times failed tests just because of typo... And I'm really surprised this feature is not popular at all... Re: Missing Objects/NameMapping/Function(Function Reference) should show in TCwahou, nothing more on that?! MKozinets am i missing something, or is it a too big piece to implement??Re: Being able to compare images with a tolerance percentage @cunderw PixelTolerance is not a percentage... so almost useless mgroen2 your feature request is more something like "search an image inside another image" as a size difference tolerance Here i'm only suggesting an acceptable percentage of differences between 2 images of same size. Re: Missing Objects/NameMapping/Function(Function Reference) should show in TCI don't understand how this feature is still not here.... !!!Being able to compare images with a tolerance percentage My wish is just to add a value between 1 and 100 to the compare function parameters. It represents the percentage of similitude of the images : in many cases images are not exactly the same but are similar enough to be considered equal. If the calculated similitude of the 2 images is equal or superior to the parameter, then it returns true, else false. Re: Implement scan option (or update namemapping) during test runColin_McCrae Indeed, applications can have a high level of complexity, that's why i said " in a few minutes for basic situations". When i'm speaking about a path to a sreen, i don't think about an URL, but more about something like a list of actions, without all the controls you have in a test. Even in complex situation like you mention, it can be really faster.Re: Implement scan option (or update namemapping) during test runRegarding the scan without a run question, there is a time issue here. Even if time is not the most important point in automation, running a whole campaign can take hours. If you run all your tests, you have then to wait hours before updating your tests and run them again. With a scan option, you may declare the different screens of your application, with a path to it. Even with a lot a different screens, this doesn't seem to be lot of work as the path shouldn't evolve so often. The scan can then be performed in a few minutes for basic situations. As the goal here is to perform the tests asap, with reliable results, running the test campaign twice is not an option imo...Re: Implement scan option (or update namemapping) during test run Happy I got you convinced :smileywink: