andrewa
Contributor
Joined 8 years ago
User Profile
User Widgets
Contributions
Closing Window with Unexpected Window Handler is aborting entire test run
So I have a suite of Windows tests. I've been having an error show up in the application. I want to be able to close it and fail the currently running keyword test and then continue on with the rest of the suite. I was under the impression that if I wrote an OnUnexpectedWindow function and closed the window, Test Complete wouldn't abort the entire test run. My code is closing the window, yet the entire suite run gets stopped. Do I need to alter my playback settings at all? Is it something else I'm doing wrong? Is the documentation about the OnUnexpectedWindow wrong? I've attached a picture of the last few lines of the log, my playback settings, and the event handler settings. The following is my event handler code: //USEUNIT CommonScripts function GeneralEvents_OnLogError(Sender, LogParams) { if (LogParams.MessageText == 'The operation cannot be performed, because the user session is locked.' || LogParams.MessageText == 'The operation cannot be performed, because the user session is disconnected.') { BuiltIn.ShowMessage ('Screen is locked. Perform the last action manually then continue test execution ...'); Runner.Pause (); LogParams.Locked = true; } else { Runner.Stop(true); } } /* if (LogParams.MessageText == 'The operation can not be performed, because the user session is locked.') { Log.Warning (LogParams.MessageText, LogParams.AdditionalText); BuiltIn.ShowMessage ('Screen is locked. Perform the last action manually then continue test execution ...'); Runner.Pause (); LogParams.Locked = true; } */ function GeneralEvents_OnUnexpectedWindow(Sender, Window, LogParams) { //BuiltIn.ShowMessage('Unexpected window detected. Please note any stack traces. Do not close the window. Continue Test Complete'); //Runner.Pause(); LogParams.Locked = true; CommonScripts.logWarningErrorWithStackAndPicture(LogParams.MessageText); Window.Close(); //Log.Error(LogParams.MessageText); //Runner.Stop(true); }Solved2.6KViews0likes4CommentsRe: Detecting (and pausing) on a locked session
They're running on a remote server. I'm not sure if it's a VM or not. The mouse moving script does sound interesting. I wonder if someone has an example of that. I could try the stack on warning, not sure if that would conflict with how our suite is set up, but I think i could adapt that to make it pause when it runs into an issue.1.2KViews0likes0CommentsDetecting (and pausing) on a locked session
So our group has a number of Test Complete tests that have long running database queries. I run the tests on a remote machine and sometimes the machine gets locked (due to a timeout thing) and then all the tests in our suite fail after that test. I've pursued trying to extend the timeout period so that it would be longer than the query that was being called, but the security group doesn't appear to want to let us do that. As an alternative, can Test Complete detect that the user session is locked and wait for it to become unlocked?1.2KViews0likes3CommentsRe: TestComplete 'missing' button clicks with Chrome TC 12.42 Windows 2008 Server
Final solution from the support staff: "The developers suspect that an Accessibility server was not registered on your machine for some reason. This library is a part of Windows and should be installed along with the operating system. To register the library, open the Command Prompt and execute the following command line: regsvr32 oleacc.dll" That solved the problems I was seeing.2.4KViews1like0CommentsTestComplete 'missing' button clicks with Chrome TC 12.42 Windows 2008 Server
So I got Chrome to work on our remote Windows 2008 Server, but then I started seeing some really odd behavior when running our web suite. It was having problems logging in, so I investigated and it looks like when it tries to click the 'Next' button to proceed, it clicks an area above the button. When I try to object spy the page, it actually won't highlight the Next button. Everything seems to work find on my local machine. I've attached some pictures of the behavior I'm seeing. Has anyone encountered this? I guess I can temporarily get around this by running the web portion of the suite locally until I can figure this out.Solved2.6KViews0likes3CommentsRe: Chrome Extension not working on Windows 2008 server
In case anyone else has a similar issue, support had me do the following and it started working: Open the chrome://extensions/ web page in Chrome. Locate the SmartBear Test Extension version 12.0.0 in the list of installed extensions. The extension is expected to be disabled without a possibility to re-enable it. Delete the extension from the list by clicking the Trash icon. Open the following page in the Chrome Web Store: https://chrome.google.com/webstore/detail/smartbear-test-extension/gmhjclgpamdccpomoomknemhmmialaae Install the extension by clicking the Add To Chrome button and confirming the requested permissions. Once the extension is installed, TestComplete should be able to work with Google Chrome.2.5KViews3likes1Comment