Saucelabs session/job name not set

[kerin]

With our current test configuration:

{
  "src_folders" : ["tests/javascript/nightwatch"],
  "output_folder" : "reports/nightwatch",

  "selenium" : {
    "start_process" : false,
    "host": "ondemand.saucelabs.com",
    "port": 80
  },

  "test_settings" : {
    "default" : {
      "launch_url" : "${LAUNCH_URL}",
      "silent": true,
      "desiredCapabilities": {
        "browserName": "phantomjs"
      }
    },

    "chrome34win81": {
      "launch_url" : "${LAUNCH_URL}",
      "silent": true,
      "selenium_host": "ondemand.saucelabs.com",
      "selenium_port": 80,
      "username": "${SAUCE_USER}",
      "access_key": "${SAUCE_KEY}",
      "desiredCapabilities": {
        "browserName": "chrome",
        "platform": "Windows 8.1",
        "version": "35"
      }
    },

    "ie9win7": {
      "silent": true,
      "launch_url" : "${LAUNCH_URL}",
      "selenium_host": "ondemand.saucelabs.com",
      "selenium_port": 80,
      "username": "${SAUCE_USER}",
      "access_key": "${SAUCE_KEY}",
      "desiredCapabilities": {
        "browserName": "internet explorer",
        "platform": "Windows XP",
        "version": "7"
      }
    }

  }
}

Test names aren't set as the Saucelab session/job name, so all jobs are shown as 'Unnamed job':

Is this a bug, a feature request, or am I missing something in our nightwatch.json?

[beatfactor]

the latter, check: https://github.com/beatfactor/nightwatch/blob/master/bin/nightwatch.json#L53

[kerin]

I did notice that, but then every job for a given run has the same name, so it's not much different from 'unnamed job' - what would really be useful is if each job had the name of the corresponding test, as in the second screenshot in #140

[beatfactor]

hmm, ok. So that means you need to alter the desiredCapabilities per module?

[kerin]

Ideally, yes - we're running Nightwatch tests on Saucelabs via Jenkins, so when a test fails we can see in Jenkins which test it was, but currently have no easy way to find the associated job in Saucelabs and see what actually happened in the test run.

[beatfactor]

The other saucelabs specific functionality you'll have to build in yourself, as seen in this example from the saucelabs branch:
https://github.com/beatfactor/nightwatch/blob/features/saucelabs-job-update/examples/tests/google.js

We also need to merge the changes there into master also of course.

[mam-p]

Andrei: Any idea when the test names will appear in the Sauce results without us having to build it in? I followed your example nightwatch.json, so all of my jobs are named "test-example"; it is virtually impossible to locate the failing one(s) so we can see the video from Sauce.

[beatfactor]

can we close this?

[satish2516]

If you are using java use the Desired capability as
caps.setCapability("name", "Your Job name");