WebdriverJS : driver.manage().logs().get('browser') returns empty array

Question

I have the following mocha test case, I'm trying to print the webdriver logs in the end, but its returning an empty array. The result is the same even when I pass 'browser' as argument to the logs().get(). Can someone please tell me why the logs are empty?

it('should open a url', function(done){
    var By = nemo.wd.By;
    driver.manage().logs();
    driver.get("http://www.google.com");
    driver.findElement(By.name('q')).sendKeys("webdriver");
    driver.findElement(By.name('btnG')).click()
    driver.manage().logs().get('driver').then(function(logs){
        console.log(logs);
        done();
    });
});

Maybe try driver.logs(). It looks like webdriverjs has a more direct method : http://selenium.googlecode.com/git/docs/api/javascript/class_webdriver_WebDriver_Logs.html — jrader, Aug 25 '15 at 20:45
It was because I didn't enable the logging option in the list of capabilities while creating the driver instance. Got resolved now. var pref = new webdriver.logging.Preferences(); pref.setLevel('browser',webdriver.logging.Level.ALL); pref.setLevel('driver',webdriver.logging.Level.ALL); var driver = new webdriver.Builder(). withCapabilities(webdriver.Capabilities.firefox()).setLoggingPrefs(pref). build(); — Oscar, Aug 26 '15 at 09:03

score 5 · Accepted Answer · edited Sep 15 '16 at 18:09

5

It was because I didn't enable the logging option in the list of capabilities while creating the driver instance. Resolved now with these changes.

var pref = new webdriver.logging.Preferences();
pref.setLevel('browser', webdriver.logging.Level.ALL); 
pref.setLevel('driver', webdriver.logging.Level.ALL); 

var driver = new webdriver.Builder()
    .withCapabilities(webdriver.Capabilities.firefox())
    .setLoggingPrefs(pref).build();

edited Sep 15 '16 at 18:09

budi

6,351
10
55
80

answered Mar 15 '16 at 06:13

Oscar

96
2
9

nice solution for FF but have you a solution for IE11? – Stéphane GRILLON Jun 27 '17 at 14:19
worked on `"chromedriver": "91.0.0",` nodejs >= – JRichardsz Jul 22 '21 at 05:19

Artem Vasiliev · Answer 2 · 2017-08-16T21:01:39.730

This also depends on browser driver being used - e.g. with chromedriver >= 2.29 the logs are sometimes 'late' - the logs().get('performance') promise resolves with empty array, but after waiting it resolves with data. This is the same with Oscar's capabilities tweaks. So, here's a workaround:

function getPerfLogs(driver) {
  let performanceLogs;

  return driver.wait(() => {
    return driver.manage().logs().get('performance')
      .then(v => {
        let nonEmpty = v.length > 0;
        if (nonEmpty) {
          performanceLogs = v;
        }
        return nonEmpty;
      })
  }, 1000)
  .then(() => {
    return performanceLogs;
  });
}

getPerfLogs(driver)
  .then(v => console.log('performance logs', v))

score 0 · Answer 3 · answered Dec 03 '18 at 18:14

@Artem's answer validated the behavior I was seeing, but I found a different solution for my case, using Protractor: explicitly call browser.waitForAngular() before accessing logs:

return item.click()
    .then(function() {
        // "Protractor automatically applies this command before every WebDriver action",
        // but apparently browser.manage().logs() is not an action. Without this line
        // here, logs are sometimes not picked up until some time later.
        return browser.waitForAngular()
    })
    .then(function() { return browser.manage().logs().get('browser') })
    .then(function(logs) { ... });

https://www.protractortest.org/#/api?view=ProtractorBrowser.prototype.waitForAngular

WebdriverJS : driver.manage().logs().get('browser') returns empty array

3 Answers3

Linked