Skip to main content

UI Elements


UI Elements

Simply, UI = User Interface

Consider any Application, Here I’m taking www.google.com as an example.

If you navigate to Google URL on any browser, it should be look like below.




From this, you can observe something like below in the application.
Search box, buttons (Sign In, Google Search, I’m Feeling Lucky), Google Image, Links (Gmail, Images) and many more
So, all these elements are available in user interface. Hence, we called them as “UI ELEMENTS”

We can have categorized all above elements in 2 ways
Input Elements: Search box, buttons, Google Image, Links
Output Elements: Google Result

Operations which you performed on input/output elements is called as Input / Output Actions

Input Actions: Clicks, Text Typing, Mouse Hover, Key board Shortcuts
Output Actions: Getting Text, Finding Elements, Getting Results

From above, UI elements only constructs an application, if we know how to interact with them enables you to implement UI automation much faster and easier.

All interactions with the UI can be split into input and output as discussed above. This categorization helps you better understand which actions to use in different scenarios, when to use them, and the technology behind them. These are also going to be useful when dealing with scraping (Which discuss later)

Then the very Next Question is
How to Interact with UI Elements?

Generally, when we trying to identify a person/thing we took some properties (Height, width, color). In the same way, if you want to interact with UI Elements, you’ve to consider UI Elements properties




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

Publish a Project

Publish a Project: Publishing means packaging/archiving the project. Why to Publish : Robot can execute only Packages, doesn’t run projects directly. So we need to archive all project files to a Single Package file. There are 2 Process are available 1.        If Orchestrator is connected through Robot, automatically Project archive file displayed in Packages folder. From here, we can distribute this to some other Robots 2.        If there is no connection between Orchestrator and Robot, we need place Project archive file in Packages folder manually How to Publish: 1.        Open UI Studio, Create New Project 2.        In the Setup ribbon tab, click Publish . If the project is published successfully, the Info dialog box is displayed and the project is copied to the NuGet location set in the NuGetServerUrl parameter, in the UiPath.settings...
Post a Comment
Read more

AGILE Methodology

Agile:      Ø   Agile is nothing but a Multi Iterative Cycle      Ø   It breaks the entire project into Small pieces and then do implementation iteration by iteration      Ø   At the end of every Iteration, customer uses application and gives feedback      Ø   At the end of ALL Iterations, customer will get the application as desired Various versions of Agile: Scrum:                     In Scrum, each iteration is called ‘Sprint’. So, at the end of Sprint, Customer interacts with application and provides feedback (Unlike Waterfall) 3 Roles:   Ø   Product Owner   Ø   Scrum Master       Ø    Team
Post a Comment
Read more