rraghvani
Champion Level 3Joined 4 years ago
User Profile
Champion Level 3
User Widgets
Contributions
Re: Playback - On Error: Stop and Rerun Current Items Not Working.
See Stop and Rerun the Current Test Item After an Error - when you configure your project settings according to either Approach 1 or Approach 2, TC does not rerun after an error, as stated in the documentation. For example, This appears to be a bug in TC, so I suggest opening a Support Ticket. Throwing an exception works fine - the same should also occur with Log.Error() is called.Re: Cannot select certain web elements anymore
Originally, I though this was relating to Windows Scaling not set to 100%, but it's not. Another user has also experienced the same issue here Elements detected, clicked in wrong location with Chrome | SmartBear Community . I haven't come across this issue yet, but it could be relating to the browser being updated, which has now caused TC to incorrectly identify the object in the wrong place.Re: aqUtils.Delay() vs Delay()
Delay() is a built-in global routine, and aqUtils.Delay() belongs to the aqUtils utility object. Both do the same thing. For Python 3.12 and onwards, it now treats each global as a regular scoped object In JavaScript, I always use aqUtils.Delay(), for no particular reason!Re: Unexpected Window event is fired only once.
Based on past experience, if the application throws an unexpected error message, I won’t automate it. This is mainly because the next steps may not produce the expected results due to the previous error. However, if the error message consistently appears after performing certain actions, then I can easily handle it without using event handlers. Regardless of the project settings, the event handler should be triggered, provided it meets the requirements. More information can be found in Handling Unexpected Windows.Re: Elements detected, clicked in wrong location with Chrome
Try remaining the folder %LocalAppData%\SmartBear\TestComplete (TC user settings), and then launch TestComplete Launch Chrome via Browsers.Item[btChrome].Run(), and reset all your settings. If the above fail to resolve your issue, then I can only suggest opening a support ticket.
