ContributionsMost RecentMost LikesSolutionsRe: Test Execute License Timeout Ah, get what you mean now To be honest we have always run the tests manaully with TE - its how they worked when I got involved and I'd not had expososure to the command line approach until staring with the build pipeline so didn't know any better. However, I like your idea of the testers running things with batch files - as it frees the license up on exit it makes good sense. Tks Dave Re: Test Execute License Timeout Not sure why you would say that I shouldn't let 'other' users run TestExecute ?? My colleague and I develop the tests using TestComplete and the test team run them using TestExecute during their weekly release integration testing. How else does it work ! Test Execute License Timeout I have a limited number of Test Execute licenses on my network I have set up a Team City build agant that pulls code and runs TestExcute via a command line on a test I want to run at least once a day It often fails to start as there aren't any available licenses It seems you can't node lock a TE license so atm I have to remotely kick TE instances off my license server before the CI system runs to ensure it gets a license. Obviously this is fine while I'm developing the pipeline but no good long term. Is there anyway to kill a license via a command line - that way if anyone forgets to shutdown TE (its not obvious its runnig after all - just a system tray icon thats usually hidden) at home time I could kick them off via a command from the build server or just a timer somewhere to ensure at, say midnight, there was a licesne available ? I notice the license server has a timeout period but its fixed on 12 hours - if that was variable I could experiment with that Please advise on any suitable approach to this problem... Dave SolvedRe: Name Mapping too big ? So anyone else coming across this post knows, the lock up issue was not caused ny the size or compelxity of the name mapping file - it was because source control was enabled. Once that was turned off the system ran as normal. Re: Name Mapping too big ? Hi again When I right click on the parent I just get the standard prompt as attached - nothing about recursing through parents - but it does seem to have mapped them all and that bit of the test still runs, so I guess I now plod through the rest Thanks for you help and prompt replies Dave Re: Name Mapping too big ? There are multiple parents - the button is in a grid, in a group box, in a text panel, etc, etc.. See capture2.png Re: Name Mapping too big ? Okey, dokey - indeed a mamoth task as I have 400 mapped items with that field checked ! ! In step 4 I have the option to map the objecy or the child objects If I chose object I don't get a prompt to map all teh objects in the tree - only a dialog asking me how to name this one Maybe we are on different versions ? I have 12.60.5545.7 Re: Name Mapping too big ? Thanks mate 2. Sounds like a lot of work and potential for some failures in my tests - think that needs some thought.... Cheers Dave Re: Name Mapping too big ? Thks for the detailed response 1. Is the "tools - options..." settings a PC or project setting as I am sharing the name mapping file with a colleague who is working on other tests for the same app - we are building up a library of functions to share ? 2. Not totally sure what you mean by you'll need to map any parent objects that may have been "collapsed" ? I have attached a typical part of my mapping tree view - maybe you can clarify Tks Dave Name Mapping too big ? Is there a max size for name mapping entries ? I'm writing a comprehensive test suite against a .NET desktop app and as of a couple of days ago everytime I add to the name mapping either directly with the wizard or by recording a test it takes longer and longer to responds - sometimes as long as ten minutes