ContributionsMost RecentMost LikesSolutionsObject browser crashes IE 11 with PDF open After I open a any PDF from the internet using IE11, when I use the TestComplete Object Browser and select Internet Explorer, it crashes the browser. Using TestComlete 10.5 Windows 8.1 with IE 11 the the Adobe PDF Reader Add on version 11.0.10.32 Re: Object browser crashes IE 11 with PDF open When trying to view any pdf online with the Object Browser, Internet Explorer 11 crashes. This happens on a Windows 8.1 64 bit and Adobe PDF Reader 11.0.10.32 with TestComplete 10.5. Looks like you probably get WER reports for it. Re: Can't open Clipboard error while editing keyword testsRan into this issue. Support suggested deleting %TEMP% files. Tried that and no longer get the error.OnUnexpectedWindow event handlerIs there a way to pass in additional args to OnUnexpectedWindow event handler? I would like to pass in additional info so I can better track occurrences of this event. Thanks, JeffObject Browser refreshingHow do I keep the object browser from refreshing and collapsing the object tree when trying to view objects? It can be anywhere from five to twenty seconds before a refresh. Thanks.Re: TestComplete Integration with DevSuite / DevTest from TechExcelI was able to run individual tests from DevTest. There has to be a test item in TestComplete for DevTest to be able to select the individual test to run. One of the main problems with the integration is you have to have DevTest installed on the machine that runs the automation. We have a workstation dedicated for automation which means you have to remote into the machine to run automation. So we don't really use the integration but we have been using the DevTest API for a long time. It is more useful since the api can create test cycles.command is invalid promptIs there any way to turn off the message box prompt that says the "command line is invalid" in Test Execute when it cannot find the routine? It does not return an error code until you click one of the buttons in the message box. Example: I have a list of routines that I want to run. I use a python system call to start Test Execute, if the routine doesn't exist when Test Execute starts it displays a message box with the "command line is invalid" error. I want it to continue on to the next test without having to click the button. ( Test Execute returns a 3 error code after manually click a button, which is good) Thanks function.caller and USEUNITI am running tests on a remote machine using TestExecute. I was thinking I could do a Log.SaveResultsAs() and save the results locally so management can view the errors in a browser. I wanted to save the file name of results as the function.caller + ".mht". However the function.caller does not seem to span USEUNIT For example when these two functions are in the same USEUNIT and I run test(); function test() { called(); } function called() { Log.Message(called.caller); } It prints the "function test() .... "; If I call the "Called" function from a different USEUNIT it does not print the function. Is there another way I can get the original caller name ? I only plan on doing the Log.SaveresultsAs() for errors. Thanks.Object name of focued itemI have a WPFObject of ClrClassName ButtonEx that I cannot view in the "Object Browser". I can tab over to the button and send key strokes to get the desired behavior. Are there any methods that will return the FullName of the current focused object? Re: OnStopTest and TestItemsIf I have a suite setup to run three test items. I have a an onStop event handler that is calling a unit function called logit(). function logit() { Log.Message("count:" + Project.Logs.LogItemsCount); Log.Message("childcount;" + Project.Logs.LogItem(0).ChildCount); } If I try to run the suite using TestExecute it will thow the error "parameter incorrect". It doesn't appear that TestExecute have access to the Project.Logs.LogItem(0) when the suite is running. I am assuming that the LogItem(0) does not change as Project.Logs.LogItemsCount is always zero when it iterates though the test items.