Contributions
Access to License Server: How to allow from remote location
Hi All, I have had some trouble posting to the forum so I hope this does not end up being a duplicate. We use Test Complete floating licenses and they talk to a PC that has the license server running without a problem But now we want to allow some users on Remote Virtual Test environmentthatis hosted outside our office to also run Use Test Complete to write the automated tests. I know we need to purchase and use more floating licenses, but I have been unable to find the information on how test completecomminicates with the license server. I am not sure what to "openup" or allow through on our network security, to let these external virtual machines find the license server which is hosted internally. Does it just use Http to communicate or some other protocol? I need to address this with some urgency as this project is about to ramp up and the ability to run test complet (or not) on this remote test environment, will determine whether we stick with test complete or go to anotherproduct. Also I have setup a small test environment on a remote PC, so I can test this but at the moment Test complete is running on a trial licence there so it does not even ask me for the license server. Is there a way to force it to end thetrial and ask for the license server? Thanks Bill DSolved1.6KViews0likes2CommentsRe: waitWinFormsObject not recognising objects or ignoring timeout
Thanks for the explanation but this was definately a different beast and we can only assume it was caused by corruption of the settings somewhere. We have been testing our application withtest completefor many years and never experienced this particular problem. Then basically on the day I reported the problem all of out tests were failing randomly for no apparent reason. We resolved the issue by completely uninstalling Test Complete from that test machine and reinstalling it. The tests all started working correctly with the correct timeouts (rather that what seemed like infinity) problem has notresurfaced (touch wood). It would have been nice to identify thespecific cause, but as usualwe were under great presssure to complete our testing. Thanks Bill D984Views0likes0CommentsRe: waitWinFormsObject not recognising objects or ignoring timeout
OK I have isolated the problem we are having. There appears to be something wrong with the waitWinFormsObject time out. In the example show below, the object barBottomDockSite exists but the dockGlobalAssistant does not if put a breakpoint on the line set w2=w1.waitWinFormsObject("dockGlobalAssistant",1000)and thenexecute the statement I canthen see how long before it moves to the next line in debug mode. I run the code, itquickly executes the previous statements and stops on thebreak point as expected on: set w2=w1.waitWinFormsObject("dockGlobalAssistant",1000) I then press thenkey to execute that line and it waits about 20-30 seconds (waiting for winforms object("dockGlobalAssistant") )before it goes to the next line.Also one thing I notice when we see this behaviour iss that the little progress bar that is shows when it is wating for an objectdoes not progress. Depending on the value we put into the statement, the wait progress barshows up partially populated but is not progressing. if I change the value to anything<200 or so it seems to work OK and goes to the next line almost instantly but any values higher than that (300 or 400, etc that should still be well under 1 second wait), it waits at least 25 seconds. Its as though its using some default timeout for values instead of the of the values I amspecifying. I have tried changing the Auto-wait timeout in the Default project properties to values ranging from 10 to 25000 and this makes no difference to this problem. sub igCloseGlobalAssistant dim w1,w2 set w1 = NameMapping.Sys.clp.frmCarelinkPlusMDI.waitWinFormsObject("barBottomDockSite",10000) if w1.exists then set w2=w1.waitWinFormsObject("dockGlobalAssistant",1000) if w2.exists then Log.Message("Closing Global Assistant") call w2.click(10,10) end if end if End Sub igCloseGlobalAssistantdw1,w2sw1 = NSclp.frmCarelinkPlusMDI.waitWinFormsObject("barBottomDockSite",10000) w1.exists w2=w1.waitWinFormsObject("dockGlobalAssistant",1000)iw2.exists tei983Views0likes0CommentswaitWinFormsObject not recognising objects or ignoring timeout
Test Complete 8 seems to be having problems recognising objects intermittently We use Test Complete to to test a very complex .net application. We can run the same code many times and sometimes it works and other times it stops waiting for objects even though we know they are there. We have been noticing more an more that it is having trouble identifying objects that are actually there. Even hitting pause we can then go to object in the object browser. But continuing the code it still sits there waiting for that object. The other issue is that when it gets into this 'Blind mode' where it cant seem to see things, it does not seem to be using the timeout value. For example, the code below to setto wait 5 seconds for thereminder form. It works most times but occassional the reminder is displayed, but the little playback control shows a message like "waiting for waitWinFormsObject("frmReminder") and sites there for a very very long time, its like it is ignoring the 5 second timeout we set in the code. If we hit pause button and wait a very very long time, we can go it object broweser copy path for the form and it is exactly as in in the code but it still does not find it and we dont know why it waits more than the time we have told it dim w1 set w1 =Sys.Process("CareLinkPlus").frmCarelinkPlusMDI.WinFormsObject("MdiClient", "").waitWinFormsObject("frmReminder",5000) if w1.exists then call w1.WinFormsObject("Button", "OK").click end if14KViews0likes3CommentsSince upgrading to 7.51 record scripts is incredibly slow and unusable
Hi, I have been using test complete to create tests for our .net application for many years on this same PC with Vista.Yesterday I installed the 7.51 upgrade and can no longer record tests. There is a massive delay between keystrokes or mouse clicks while recording (at least 1 second between each key) and it makes it impossible to fill in a large form now. Even from a clean start where I open test complete, go to a script file and press record (no editing in testcomplete), I start typing on the form or clicking on checkboxes and nothing happens for several seconds then the letters start appearing or checkboxes start checking at 1 or 2 secondintervals.If I play back the script it runs at full speed (faster then I originally typed). I am hoping there is a simple answer, I have tried resaving the project settings etc.If there is no answer for this I will need to roll back to an earlier version as itmakes it impossible for me to fill in complex forms for tests now. Anyone have any ideas? Also are there any script compatability issues if I roll back to a slightly earlier version? Bill D16KViews0likes1Comment