stevenmkeller
Occasional Contributor
Joined 15 years ago
User Profile
User Widgets
Contributions
Re: Unable to record in 14.30
Thanks for replying Tanya. It turned out it was an issue with the DLL's that we need to recieve from TestComplete for our application to be recognized. Anytime there is a major update and now minor updates, it looks like we have to wait for the developers to send us new DLL's related to QT. The developers got me the new DLLs yesterday and I am up and running again.1.9KViews1like1CommentRe: Unable to record in 14.30
Looks like this may be an issue with the application I am testing. I created a new project suite that would test Notepad++ and recording works fine. I added our application to the same suite and it doesn't record. We have to get special DLL's from TestComplete so it sees our program so something must have broke with those recently. I sent a support ticket and they are forwarding that information to the development team.2KViews1like3CommentsUnable to record in 14.30
Hello, I recently updated to 14.30 and now when I try to record a script, the only thing that gets added to the file is: function Test1() { } The function is completely blank. Has anyone else seen this? Is it a known issue with the latest update? Thanks!Solved2.1KViews0likes8CommentsTest Complete 9 no longer allows Regions with a / in the name
In Test Complete 8 you could create a Region with a / in the name. In Test Complete 9, you now get an error saying the name is invalid. Scripts that are brought forward from Test Complete 8 to 9 still work but you can not create new regions with a / in the name. Any chance this will get fixed soon? Anyone else experiencing this issue?24KViews0likes1CommentRe: Regions coming up different in Windows 7
Anyone have any suggestions? How can I make Windows 7 look like Windows Vista? I found one possible solution. TestComplete 8 has a new feature called Region.Check that has a ColorTolerance parameter that can fix my issue. The only problem is that I will have to change 1300 lines of code to use this new method. It would really be nice to know what changed between Windows Vista and Windows 7 that is causing this slight color difference.751Views0likes0CommentsRegions coming up different in Windows 7
I have script where I call Regions["Compare"] on about 1300 regions. I recently upgraded my computer from Windows Vista to Windows 7 operating system. When running my script on Windows Vista, everything worked as expected. Now when I run my script roughly 160 regions come up saying they are different everytime. They are all coming up different because of the OK button that appears in the dialog I am checking, the OK button is the active item in the dialog. I have ran my script and set all the regions to update and then I run my script again with the regions set to not update and they come back saying they are different. I have made sure that I have "Disable DWM before capturing image" enabled in the Default Project Properties. I also have "Update regions" enabled in Options. I have sent AutomatedQA emails stating this problem but they just responded by telling me to make sure "Disable DWM before capturing image" is enabled, which as I just stated it is. The other option they gave me is to "ignore the button" which would be a real pain cause I would have to do this with 160 regions. This is only a problem on Windows 7. Has anyone else ran into a problem like this on Windows 7? Everything worked perfectly fine on Windows Vista. If you need anymore info please let me know. Thanks13KViews0likes4Comments