V2 - Error TypeError: Cannot read property 'toLowerCase' of undefined at new Promise (<anonymous>) when running tests with AWS device farm settings

[mostmentor]

Describe the bug

I'm trying to run tests on AWS device farm after upgrading to Nightwatch v2 but getting this error
TypeError: Cannot read property 'toLowerCase' of undefined at new Promise (<anonymous>)
The test is running when adding other configuration (BrowserStack & local chrome webdriver)

Sample test

sampleTest.js

describe('Demo test Ecosia.org', function() {
  test('search for nightwatch', function(browser) {
    browser
      .url('https://www.ecosia.org/')
      .waitForElementVisible('body')
      .assert.titleContains('Ecosia')
      .assert.visible('input[type=search]')
      .sendKeys('input[type=search]', 'nightwatch')
      .assert.visible('button[type=submit]')
      .click('button[type=submit]')
      .assert.containsText('.mainline-results', 'Nightwatch.js')
      .end();
  })
});

Run with command

$ nightwatch Ecosia.js --verbose

Verbose output

debug.log

No output

Configuration

nightwatch.json

{
  "src_folders": "./tests",
  "page_objects_path": [
    "./page_object"
  ],
  "globals_path": "globals.js",
  "webdriver": {
    "keep_alive": true
  },
  "custom_commands_path": [
    "./lib/custom_commands",
    "./node_modules/nightwatch-xhr/es5/commands"
  ],
  "custom_assertions_path": [
    "./node_modules/nightwatch-xhr/es5/assertions"
  ],
  "test_workers": {
    "enabled": false,
    "workers": 0
  },
  "test_settings": {
    "default": {
      "selenium": {
        "start_process": false,
        "host": "testgrid-devicefarm.us-west-2.amazonaws.com",
        "default_path_prefix": "generated from aws device farm sdk",
        "port": 443
      },
      "skip_testcases_on_fail": false,
      "silent": true,
      "exclude": [
        "tests/*sample*.js"
      ],
      "request_timeout_options": {
        "timeout": 180000,
        "retry_attempts": 0
      },
      "output_folder": false,
      "end_session_on_fail": false,
      "desiredCapabilities": {
        "browserName": "chrome",
        "resolution": "1920x1080",
        "javascriptEnabled": true,
        "acceptSslCerts": true
      },
      "capabilities": {}
    }
  },
  "live_output": true,
  "detailed_output": true,
  "test_runner": {
    "type": "default",
    "options": {
      "bail": "false",
      "retries": 0
    }
  }
}

Your Environment

Executable	Version
nightwatch --version	2.0.0-beta.1
npm --version	6.14.15
node --version	14.18.0

Browser driver	Version
Chrome	Latest

[vaibhavsingh97]

Thanks for reporting the issue, can you please share the verbose log with us, it will help us a lot to understand the problem.

[mostmentor]

It's not even starting session to start logging any verbose

[mostmentor]

I've found the problem it's the "capabilities": {} It was required to be added in nightwatch v1.7 but looks like it causes conflict here
If you can show to the user which line is causing the problem it would be much easier to catch the problems afterwards

[gravityvi]

Nightwatch uses capabilities instead of desiredCapabilities if capabilities is present and is an object.

nightwatch/lib/core/client.js

Line 432 in 1277601

setInitialCapabilities(value) {

Using default browser(firefox) in case no browserName is found in capabilities will resolve this issue.

[AutomatedTester]

Some of the details of what capabilities we need to be aware of can be found in the webdriver spec