CODEWITHSUNDEEP
javagoogle-chromeseleniumselenium-chromedriverserenity-bdd
BobbyB
BobbyB

Reputation: 493

Chrome is being controlled by automated test software

I am running automated tests in Chrome with Serenity BDD (Selenium).

I had to download a new ChromeDriver, because my tests could not run -> The test would open ChromeDriver but could not "Browse as user". When I googled the issue, they said I had to update ChromeDriver.

So I updated ChromeDriver to version 2.28 and I also updated the Chrome version to Version 57.0.2987.98.

But now - EVERY TIME I run my tests this annoying text comes up:

Chrome is being controlled by automated test software

And it asks me if I want to save password. (I can't add pictures because I don't have enough "points")

In the previous version, I had managed to block these 2 things by:

public class CustomChromeDriver implements DriverSource {

    @Override
    public WebDriver newDriver() {
        try {
            DesiredCapabilities capabilities = DesiredCapabilities.chrome();
            Proxy proxy = new Proxy();
            String proxyServer = String.format("AProxyIDontWantToDisplay", System.getenv("proxy.username"), System.getenv("proxy.password"));
            proxy.setHttpProxy(proxyServer);
            capabilities.setCapability("proxy", proxy);
            ChromeOptions options = new ChromeOptions();
            options.addArguments(Arrays.asList("--no-sandbox","--ignore-certificate-errors","--homepage=about:blank","--no-first-run"));
            capabilities.setCapability(ChromeOptions.CAPABILITY, options);
            ChromeDriver driver = new ChromeDriver(capabilities);
            return driver;
        } catch (Exception e) {
            throw new Error(e);
        }
    }

    @Override
    public boolean takesScreenshots() {
        return true;
    }
}

I know there is this one (A link to same issue), but there are too many answers that don't work.

Anybody that knows how to remove that?

Upvotes: 48

Views: 148629

Answers (22)

James Ejercito
James Ejercito

Reputation: 1

Worked for me in 2024

For people using Selenium Javascript. The solution that worked for me is

options.excludeSwitches('enable-automation');

Upvotes: 0

rajeev ranjan
rajeev ranjan

Reputation: 31

With Selenium 4.23.0, we are able to avoid automated detection.

var options = new ChromeOptions();
options.addArguments("enable-automation");
options.addArguments("disable-infobars"); // optional, it will just disable info bar
WebDriver driver=new ChromeDriver(options);

Upvotes: 0

Ellie Winer
Ellie Winer

Reputation: 1

This worked for me when nothing else did. It allows the page to skip past the automated test software:

captcha = driver.find_element(By.LINK_TEXT, "Try different image")

captcha.click()

Upvotes: 0

Long Nguyễn Văn
Long Nguyễn Văn

Reputation: 69

You can hide "Chrome is being controlled by automated test software" by following. If you are using serenity version 3.2.4 or 3.1.0, you can update

serenity.conf

as follows:

webdriver {
    driver = chrome
}
chrome_experimental_options {
    excludeSwitches = enable-automation
}

In higher versions, it may not work. And I found it works fine in the above 2 versions.

Upvotes: 0

NSR
NSR

Reputation: 1

ChromeOptions options = new ChromeOptions();
options.AddExcludedArgument("enable-automation");// Only for this line notification hide
WebDriver driver = new ChromeDriver(options);

Upvotes: 0

itirazimvar
itirazimvar

Reputation: 919

I tried almost every option from GitHub currently with those options I don't get additional browser page.

chrome_options = Options()
chrome_options.add_argument("--remote-debugging-port=9222")
chrome_options.add_argument("--headless") # this changes the behavior 
driver = webdriver.Chrome(options=chrome_options)

Version info

2023-12-28 Thu 17:55  
google-chrome --version
Google Chrome 120.0.6099.129
pip list | grep selenium
selenium               4.16.0

Upvotes: 0

Prottoy
Prottoy

Reputation: 131

Works on 2022

remove Chrome is being controlled by automated test software in python

from selenium.webdriver.chrome.webdriver import WebDriver
from selenium.webdriver.chrome.options import Options

chromeOptions = webdriver.ChromeOptions()
chromeOptions.add_experimental_option("excludeSwitches", ['enable-automation']);
URL = "https://google.com/"
driver.get(URL)

Upvotes: 11

Ashu
Ashu

Reputation: 49

It works for me, with this code I am able to disable Chrome is being controlled by automated test software as well as the Save password popup`

    Map<String, Object> prefs = new HashMap<String, Object>();
prefs.put("credentials_enable_service", false);

ChromeOptions options = new ChromeOptions();
options.setExperimentalOption("excludeSwitches",Collections.singletonList("enable-automation"));
options.setExperimentalOption("prefs", prefs);

WebDriver driver = new ChromeDriver(options)

Upvotes: 2

Lo&#239;c Joachim
Lo&#239;c Joachim

Reputation: 109

It took a lot of fiddling but eventually I found a combination of flags that works in 2021!

This tells Chrome to ignore all SSL errors, disables the "Chrome is being controlled by automated test software" message and starts in full screen. Add it to the Target field of your shortcut:

"C:\Program Files\Google\Chrome\Application\chrome.exe" --ignore-certificate-errors --test-type=webdriver --start-fullscreen

Upvotes: -1

Mika Berglund
Mika Berglund

Reputation: 61

Tried many of these suggested solutions, but none of them worked. OK, my code is in C#, so there might be some differences in the WebDriver implementations for different platforms.

Anyway, the solution that I got working was using the following options for Chrome when running on .NET.

var options = new ChromeOptions();
options.AddExcludedArguments("enable-automation");

On .NET there doesn't seem to be any setExperimentalOption() method on the ChromeOptions class.

Upvotes: 5

JM217
JM217

Reputation: 737

"disable-info" switch is not supported anymore for the latest chromedrivers. (at least 76.0).
@Rajeev's answer works and here I write the counterpart for C#.

ChromeOptions chromeOptions = new ChromeOptions();
chromeOptions.AddAdditionalCapability("useAutomationExtension", false);
chromeOptions.AddExcludedArgument("enable-automation");
Driver = new ChromeDriver(chromeOptions);

Upvotes: 14

Anuj Teotia
Anuj Teotia

Reputation: 1323

Previously, passing the "disable-infobars” ChromeOption to the WebDriver prevented Chrome from displaying this notification. Recently, the "disable-infobars" option has been deprecated and no longer removes the notification. The current workaround for this is to pass in an option called "excludeSwitches" and then exclude the "enable_automation" switch.

ChromeOptions options = new ChromeOptions(); 
options.setExperimentalOption("excludeSwitches", new String[]{"enable-automation"}); 
WebDriver driver = new ChromeDriver(options);

Upvotes: 34

Sodium
Sodium

Reputation: 1066

"disable-infobars" flag has been deprecated, but you can avoid this message by adding the following:

ChromeOptions chromeOptions = new ChromeOptions();
chromeOptions.setExperimentalOption("useAutomationExtension", false);
chromeOptions.setExperimentalOption("excludeSwitches",Collections.singletonList("enable-automation"));    
WebDriver driver = new ChromeDriver(chromeOptions);

Upvotes: 3

JexAce
JexAce

Reputation: 3

You may use this 

options1.add_argument("--app=https://www.google.com.ph")

Upvotes: 0

Rajeev
Rajeev

Reputation: 109

ChromeOptions options = new ChromeOptions();
options.setExperimentalOption("useAutomationExtension", false);
options.setExperimentalOption("excludeSwitches",Collections.singletonList("enable-automation"));    
WebDriver driver = new ChromeDriver(options);

Use the above codes for latest Chrome drivers.

Upvotes: 9

Tree Go
Tree Go

Reputation: 1

It works for me by using addArguments(array("disable-infobars"))

This is for facebook/php-webdriver

$options = new ChromeOptions();
$options->addArguments(array("disable-infobars"));
$capabilities = DesiredCapabilities::chrome();
$capabilities->setCapability(ChromeOptions::CAPABILITY, $options);
$this->driver = RemoteWebDriver::create('http://localhost:4444/wd/hub', $capabilities);

Upvotes: 0

MatthewThomas.dev
MatthewThomas.dev

Reputation: 1045

Protractor solution:

I arrived here searching for a Protractor solution, if useful for anyone I found, with help from the above answers; with Protractor you can add Chrome specific options to the chromeOptions object, within the capabilities object in the protractor.config file, for example to use the disable-infobars option discussed above use the following:

capabilities: {
  'browserName': 'chrome',
  'chromeOptions': {
    'args': ['disable-infobars']
  }
},

To use the enable-automation also discussed above:

capabilities: {
  'browserName': 'chrome',
  'chromeOptions': {
    'excludeSwitches': ['enable-automation']
  }
}

disable-infobars is preferred in my circumstances.

Upvotes: 2

cwnewhouse
cwnewhouse

Reputation: 189

While the disable-infobars route will work, it will likely suppress the infobar in all cases (as suggested here), not just the case that the OP is referring to. This is overkill at best, and could lead to unexpected and inexplicable behavior in the future if you are not getting some important message.

I think it's better to leverage the provided enable-automation switch by disabling it in the excludeSwitches area of your config/setup while doing nothing with regards to disable-inforbars. The enable-automation switch's description:

Inform users that their browser is being controlled by an automated test.

For nightwatch.conf.js it would look something like this (and worked for me):

desiredCapabilities: {
  ...
  chromeOptions: {
    excludeSwitches: ['enable-automation'],
    ...
  }
}

This should only do what we are after: getting rid of that specific pesky message!

Edit [2017-11-14]: This is now causing an even more annoying Disable Developer Mode Extensions alert/warning. I've tried every relevant-looking flag/switch I could find that might help, but to no avail. I've filed a bug with Chromium, so we'll see and I'll try to swing back through here if I get a resolution.

Upvotes: 4

PDD
PDD

Reputation: 314

If anyone is using Rails 5.1+, which changed the testing structure a bit and Capybara is configured in this file now for system tests:

application_system_test_case.rb

You can add "args" in the options for driven_by like this:

driven_by :selenium, using: :chrome, screen_size: [1400, 1400], options: { args: ["--disable-infobars"] }

Upvotes: -1

Mesut GUNES
Mesut GUNES

Reputation: 7401

May someone needs this for Capybara, Watir should be like this:

Capybara.register_driver :chrome do |app|
  $driver = Capybara::Selenium::Driver.new(app, {:browser => :chrome, :args => [ "--disable-infobars" ]})
end

Upvotes: 2

Sasank Sarma
Sasank Sarma

Reputation: 11

Map<String, Object> prefs = new HashMap<String, Object>();
//To Turns off multiple download warning
prefs.put("profile.default_content_settings.popups", 0);

prefs.put( "profile.content_settings.pattern_pairs.*.multiple-automatic-downloads", 1 );

//Turns off download prompt
prefs.put("download.prompt_for_download", false);
                    prefs.put("credentials_enable_service", false);
//To Stop Save password propmts
prefs.put("password_manager_enabled", false);

ChromeOptions options = new ChromeOptions();
options.addArguments("chrome.switches","--disable-extensions");
//To Disable any browser notifications
options.addArguments("--disable-notifications");
//To disable yellow strip info bar which prompts info messages
options.addArguments("disable-infobars");

options.setExperimentalOption("prefs", prefs);
System.setProperty("webdriver.chrome.driver", "Chromedriver path");
options.addArguments("--test-type");
driver = new ChromeDriver(options);
Log.info("Chrome browser started");

Upvotes: 0

jgode
jgode

Reputation: 1869

Add this to the options you pass to the driver:

options.addArguments("disable-infobars");

Upvotes: 39

Related Questions