Skip to main content

Automation Debugging


Automation Debugging:
   It is a process of identifying & removing errors from a project
   Logging & Breakpoints are two techniques which helps to the project as error-free.
   Logging – Display details about what is happening in a project in Output panel.
   Breakpoints – It enables user to pause the execution, find out the status at particular point in Project.


Example:
1.       Select the True branch between the Input Dialog and Flow Decision activities, and press Delete. The True branch has been deleted.
2.       Add a Log Message activity next to the Flow Decision.

3.       Connect the Log Message activity to the True branch of the Flow Decision and to the Input Dialog activity. The automation should look as in the following screenshot.




4.       Select the Log Message. The Properties panel is updated accordingly.
5.       From the Level list, select Error, and in the Message field type what error message to be returned, such as "Invalid user name." When you execute the project, the error message is displayed in the Output panel every time the user does not fill in the Hello World window.
6.       Press F5 to execute the automation and do not fill in the Hello World window the first time when you are prompted. The Output panel has logged the error message you added at step 5.



7.      On the Execute tab, in the Debug group, from the Options menu, select Log Activities. This will display logs in the Output panel.
8.       Select the Log Message activity and, on the Execute tab, in the Debug group, click Toggle Breakpoint. Note that a small that a red dot with white stripes is displayed next to it. This signals that this activity has a breakpoint applied.



9.    On the Execute tab, in the Launch group, click Start Debug. The debugging process starts and the Hello World window is displayed.
10.  Do not fill in the field and click OK. The breakpoint has been triggered and, as a result, the automation stopped. Note that, in the Output panel, the error and all steps covered until now have been logged, and the Log Message activity is highlighted.



11.   On the Execute tab, in the Launch group, click Stop. An information dialog box is displayed, letting you know that the debugging process has been canceled. 

Comments

Post a Comment

We appreciate your valuable Suggestions/Feedback

Popular posts from this blog

Types of Recording

Types of Recording: 4 types of recording modes are available Ø   Basic Ø   Desktop Ø   Web Ø   Citrix 2 ways of Recording Ø   Automatic Ø   Manual Basic – generates a full selector for each activity and no container, the resulted automation is slower than one that uses containers and is suitable for single activities. Desktop – suitable for all types of desktop apps and multiple actions; it is faster than the Basic recorder, and generates a container (with the selector of the top-level window) in which activities are enclosed, and partial selectors for each activity. Web – designed for recording in web apps and browsers (supported: Internet Explorer, Google Chrome), generates containers and uses the Simulate Type/Click input method by default. Citrix – used to record virtualized environments (VNC, virtual machines, Citrix, etc.) or SAP, permits only image, text and keyboard automation, and requires explici...
Post a Comment
Read more

RPA Life Cycle

RPA Life Cycle: It is similar to software development life cycle with some minor changes. Technically, we called it as ‘ Life Cycle of a Bot’   Analysis:           ·     RPA Cycle begins from ‘ Analysis ’ phase.           ·     In this, Business Team & RPA Strategist/Architect identifies business process to automate           ·     After finalizing feasibility on process, implement plan of work (which includes documentation, Resources count & Time  ...) Development:          ·       Dev. Team starts working on requirements wrt to Environment.          ·       We called this phase as ‘ Bot Development ’          ·       Based on Tool selection , Limited/No coding is required ...
Post a Comment
Read more

Saving your files as macro-enabled workbooks

It's really important that whenever you make something in the VBE(Called Visual Basic Editor), whenever you insert a module and you put code in there, you have to make sure that you're saving your workbook as not just a regular XLS exe file , but XLS EM .So, it's called the Macro Enabled Workbook. How can you do that , 1)Open Excel, Go into File 2)Select Save As option 3)And for the file type, you can choose here instead of Excel workbook, you can choose Excel Macro-Enabled Workbook.Again. Take a Note Of : If you've any sort of macros or you write code in a sub or a function, it has to be a Macro-Enabled Workbook, if you just save it as an Excel workbook, it's going to lose all of those modules and the code that you put in there.
Post a Comment
Read more