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

Popular posts from this blog

Brief Overview of RPA

Brief Overview of RPA:     §   In short, it’s a way for machines to replace human workers in regular activities done across the organization.     §   It works on both Front End & Back End applications/operations.     §   BOT provides Virtual automation agents , it acts like MIMIC HUMANS .     §   BOT ’s available in Clouds/Servers     §   BOT is nothing but a configurable software set up, works only on rule-based triggers     §   It automates Non-Value –added works     §   It is a Sub Domain of BPMS (Business Process Management Software)

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 ...

Why RPA, Why not Other Tools

Like below there are several features compared to other tools RPA QTP/UFT SELENIUM Commercial Commercial Open Source Less Programming Moderate Programming More Programming License Cost is Less License Cost is More No license cost Free Version No/Minimal additional cost for extra bots Add-Ins Additional cost is very high Free/Paid Add-Ins are available ROI is more ROI is less compare to RPA ROI is more as Open Source Error rate almost to Zero Error rate is moderate Error rate is moderate Customer Satisfaction is high Customer Satisfaction is Moderate Customer Satisfaction is Moderate User Friendly User Friendly Complex 24*7 support 24*7 support No Support