ddguy
Occasional Contributor
Joined 6 years ago
User Profile
User Widgets
Contributions
Help With Object Not Found Error
Hi, I do QA for a desktop application. This application has UI threads that are sometimes slow, which I believe is causing our nightly Test Complete tests to fail with "the object does not exist" errors. Some important notes: - In the screenshots of the errors, I can see the button/window/object which indicates that it exists, however TestComplete can not find it - TestComplete keeps searching for the object, in a seemingly recursive fashion (see image below) Is there a way to retry the last step that caused the logErrorHandler event? Maybe within the logErrorHandler code? Or is there some other solution to this? I have tried using the Aliases.myApp.Refresh() within the error handler and it does not help. I would like to avoid using delays between steps as that would make our tests too long. I also would like to avoid writing custom code which write the test name into a file and re-runs the tests that way, since the errors would still show up and fail the Jenkins job, which is what we use to run the nightly tests on a VM. Any help would be very much appreciated!Re: TestComplete on Unexpected Window handler not working
Hi Alex, Yes we have an unexpected window event set up, which is connected to a method in a file which I have tested and certainly does work however now I am wondering what the priority of that custom handler is. Does TC first try the default handler then the custom unexpected event handler? It seems like it skips the default handler and enters the custom unexpected window handler. Also I have heard from other discussion on this board that anything that has to do with the expected application will never be an unexpected window, only truly unexpected windows such as a windows update or such. Is this true? Thanks, DanRe: TestComplete on Unexpected Window handler not working
Hi Alex, All of our test items use the project's 'On error' property, which in turn is configured to continue running in the event of any errors. Are there any other settings that may overwrite this, or any other checks we should do to make sure the "on unexpected window" behavior is reached? Many thanks, DanRe: TestComplete on Unexpected Window handler not working
Hi Marsha, I have looked at the remarks, all of our popup windows are visible and of type java.swing. From my conclusion and as stated in the documentation, expected behavior is defined when recording the test, and anything outside of that is considered "unexpected". This means that, for example, whn trying to close our application, if there was a popup saying "your changes may not have been saved" which has never showed up before, it would be considered an unexpected window correct? We have had this exact scenario happen with the unexpected window handler not working... is there anything we can do? Thanks for the quick reply, DanTestComplete on Unexpected Window handler not working
Hi there, We have a large java swing based application with many modal pop ups and windows. In our project properties -> playback, under "On Unexpected window" I have enabled the checkboxes that press 'esc', 'enter', 'send the close command', and 'click on focused control'. However this has never worked (even since TestComplete 8) when we encounter unexpected windows from our application. I am wondering if those modals/windows that show up unexpectedly during the test are not considered an "unexpected" windows to TestComplete, since it is still part of our application. If that is the case, we would have to write specific handlers depending on which modal/window exists (ex: if (Aliases.blah.exists(1000) do....) which would be very slow and unnacceptable. Is there a way to define which windows would be "unexpected" or some other alternative solution? Thanks, Dan
