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

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)
2 comments
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

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
1 comment
Read more