Sign in to follow this  
Followers 0
Automationuser

Using debugger tool on automated scripts

2 posts in this topic

#1 ·  Posted (edited)

Hello,

I have written autoit scripts to automate a windows application. Script failed due to a bug in the application and I used the Graphical debugger to debug it.

I used the single step option in the debugger tool to find the error but was not able to find it.

So is there any settings I need to follow to trace this error??

For ex. I am trying to click on a button in my application and If the button is not available does the debugger tool throws any error in the program trace box?

And also when I press F8 the debugger tool doesn't switch back and forth between the application and autoit debugger tool. Am I missing something here?

Edited by Automationuser

Share this post


Link to post
Share on other sites



I can't say anything about the debugger tool (never used it myself).

But I can say that you should add some error checking code to your script. Clicking on a button that does not exist gives you a return value of 0. This error should then be handled by your script.


My UDFs and Tutorials:

Spoiler

UDFs:
Active Directory (NEW 2017-04-18 - Version 1.4.8.0) - Download - General Help & Support - Example Scripts - Wiki
OutlookEX (NEW 2017-02-27 - Version 1.3.1.0) - Download - General Help & Support - Example Scripts - Wiki
ExcelChart (2015-04-01 - Version 0.4.0.0) - Download - General Help & Support - Example Scripts
Excel - Example Scripts - Wiki
Word - Wiki
PowerPoint (2015-06-06 - Version 0.0.5.0) - Download - General Help & Support

Tutorials:
ADO - Wiki

 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0