UiPatjh chrome web driver mode

Help Activities
, ,
1

What is the differenc ebetween headless and Use GUI in webdriver mode option?
2. which one to use an dwhen ?
3. which one is the fastest?

1 Like
2

@Ritaman_Baral

  1. Headless works without actual gui or user interface
  2. This helps in saving the time to load as the actual gui is jot loaded
  3. Depending on the usecase…if headless is supported then we can gow ith it which helps in parallely working on multiple browser instances
  4. With gui parallely working with different would be difficult
  5. Few downsides are if anything needs to be scrapped from ui like the text that appears when hivered over or few pages need gui and a click to happen manually.m etc are few instances where it cannot work

Hope this helps

Cheers

1 Like
3

Hi

Let’s go one by one

Headless mode means that the browser is launched without a graphical user interface (GUI). This means that the browser window is not displayed on the screen. Headless mode is often used for automated testing and web scraping, as it can be faster and more efficient than using a GUI browser.

Use GUI mode means that the browser is launched with a GUI. This is the default mode for UiPath web browser activities. Use GUI mode is useful for debugging and monitoring automation scripts, as it allows you to see what is happening on the screen.

When to use headless mode

  • When you need to automate a web browser task quickly and efficiently.
  • When you are running automation scripts on a server or other headless machine.
  • When you do not need to see what is happening on the screen.

When to use Use GUI mode

  • When you are debugging or monitoring automation scripts.
  • When you need to interact with elements on the screen that are not easily accessible using headless mode.
  • When you are running automation scripts on a machine that does not have a graphical display.

Headless mode is generally faster than Use GUI mode, as it does not have to render the browser window on the screen. However, the speed difference can vary depending on the specific automation task and the machine that the automation is running on.

Example

Suppose you are automating the process of logging into a website and extracting some data from the homepage. You could use either headless mode or Use GUI mode to automate this task.

If you use headless mode, the browser would be launched without a GUI and the automation would run in the background. You would not be able to see what is happening on the screen, but the automation would be faster than if you used Use GUI mode.

If you use Use GUI mode, the browser would be launched with a GUI and you would be able to see what is happening on the screen. This would be useful if you need to debug the automation or if you need to see the data that is being extracted from the website.

Reference document

About the WebDriver protocol:

Hope this helps

Cheers @Ritaman_Baral

1 Like
4

Really liked your explanation!!!
I have one more question
So basically if a website supports headess or gui how to identify?
Do we need to use hit and trial approach?

1 Like
5

Well Automation projects with the WebDriver protocol can be created for the following browsers:

  • Google Chrome
  • Mozilla Firefox
  • Microsoft Edge Browser

Automations via the WebDriver protocol do not require you to install the corresponding browser extensions, but they do require the corresponding browser webdriver executable.

Although the WebDriver protocol can be used for both headless and visual browser automations, it is not meant to replace the UiPath browser extensions, giving you the freedom to use whichever option suits you best.

Have a view on this thread to know how to configure headless automation

Hope this clarifies

Cheers @Ritaman_Baral

6

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.