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

Variables, Data Types and Math Operations

  In order to do anything interesting in a program, we must have the ability to store and manipulate values. What allows us to do that are what we call variables. Now a variable, simply put, is just named data storage. Now Java is a strongly ‑ typed language. Now what that means is that when we declare a variable like, in this case, we have a variable named data Value, we have to specify the type of that variable, in this case, it's what we call an int, something that can store integers. So, what that means is that the data Value variable can only store things that are compatible with the type int. As we go through the course, we'll talk about this idea of one type being compatible with another. Now when we declare a variable, we can, of course, then assign a value to it, so our variable data Value now holds the value 100. Now when we use variables, we can do it the way we've done here where we declare it, then assign it, or as a matter of convenience, we can declare them a...
Post a Comment
Read more

ClaimCenter

Claim Center is a web-based enterprise software application designed to manage the process of reporting, verifying, and making payments on claims against a policy. It manages the claims process from first notice of loss through execution of financial transactions, including the payment and setting of reserves. CC Functionality involves Group-based ownership of claims and claim sub objects Claim Financials Address book integration Workspace to manage claims process Distributed collaboration Activity coordination Worker and claim management
Post a Comment
Read more

JRE vs. JDK

  The JRE and the JDK are two terms you hear people mention very frequently in the Java world, and what they are the two parts that we need in order to run and create Java applications. The JRE is the Java Runtime Environment. JDK is the Java Development Kit. And so, the JRE is what you require in order to run Java applications, and end users normally install the JRE. They're the ones who are going to run our apps. The JDK provides the tools that we need to create Java apps. So, normally, developers are the ones who install the JDK on their machines. And in order to develop apps, you need to run them, so the JDK installation includes a JRE. So how does all this work together? If we sit down, and we type up a Java source file with our program code inside of it, and we want to go ahead and run that in some host environment, how do we do it? A host environment might be Windows, Linux. It could be Mac. It could even be a browser. It might be a phone running Android. How do we get from ...
Post a Comment
Read more