CODEWITHSUNDEEP
javascriptselenium-chromedrivernightwatch.jsselenium-server
Kats
Kats

Reputation: 41

Chromedriver doesn't quit after test finishes

I'm using nightwatch framework for my tests. I have installed selenium-server via this command into my project folder "npm install --save-dev selenium-server", and a chromedriver via npm install --save-dev chromedriver. I run my tests with this command : ./node_modules/.bin/nightwatch -e chrome --tag [test name]. My nightwatch.json file looks like: 

{
  "src_folders": [
    "tests"
  ],
  "output_folder": "reports/XMLReports",
  "custom_commands_path": [
    "commands",
    "node_modules/nightwatch-custom-commands-assertions/js/commands",
    "./node_modules/nightwatch-commands/commands"
  ],
  "custom_assertions_path": "node_modules/nightwatch-custom-commands-assertions/js/assertions",
  "page_objects_path": [
    "pages_lms",
    "pages_app"
  ],
  "globals_path": "./globalsModule.js",
  "selenium": {
    "start_process": true,
    "server_path": "./node_modules/selenium-server/lib/runner/selenium-server-standalone-3.11.0.jar",
    "log_path": "log/",
    "host": "127.0.0.1",
    "end_session_on_fail" : true,
    "port": 4444,
    "cli_args": {
      "webdriver.chrome.driver": "./node_modules/chromedriver/lib/chromedriver/chromedriver",
      "webdriver.ie.driver": "",
      "webdriver.firefox.profile": ""
    }
  },
  "test_settings": {
    "chrome": {
      "selenium_port": 4444,
      "selenium_host": "localhost",
      "silent": true,
      "screenshots": {
        "enabled": true,
        "path": "screenshots/"
      },
      "desiredCapabilities": {
        "browserName": "chrome",
        "args": [
          "disable-web-security",
          "ignore-certificate-errors",
          "--test-type "
        ]
      }
    }
  }
}

the problem is that after each test the chromedriver doesn't quit, and if I'd run 10 tests one by one I would get 10 chromedriver up.

If I would add globals.js file and put the path into my nightwatch.json:

   var chromedriver = require('chromedriver');
module.exports = {
  before : function(done) {

    chromedriver.start();

    done();
  },

  after : function(done) {
    chromedriver.stop();

    done();
  }
};

that would open another chromedriver (that means two chromedrivers for one test ), but one chromedriver would be finished and another still not.

Here are the logs for one test:

2:26:09.135 INFO [GridLauncherV3.launch] - Selenium build info: version: '3.11.0', revision: 'e59cfb3'
12:26:09.137 INFO [GridLauncherV3$1.launch] - Launching a standalone Selenium Server on port 4444
2018-04-13 12:26:09.292:INFO::main: Logging initialized @614ms to org.seleniumhq.jetty9.util.log.StdErrLog
12:26:09.629 INFO [SeleniumServer.boot] - Welcome to Selenium for Workgroups....
12:26:09.630 INFO [SeleniumServer.boot] - Selenium Server is up and running on port 4444
12:26:10.353 INFO [ActiveSessionFactory.apply] - Capabilities are: Capabilities {acceptSslCerts: true, args: [disable-web-security, ignore-certificate-errors, --test-type ], browserName: chrome, javascriptEnabled: true, name: Admin Login Test}
12:26:10.355 INFO [ActiveSessionFactory.lambda$apply$11] - Matched factory org.openqa.selenium.remote.server.ServicedSession$Factory (provider: org.openqa.selenium.chrome.ChromeDriverService)
Starting ChromeDriver 2.37.544337 (8c0344a12e552148c185f7d5117db1f28d6c9e85) on port 12055
Only local connections are allowed.
12:26:11.893 INFO [ProtocolHandshake.createSession] - Detected dialect: OSS
12:26:12.491 INFO [RemoteSession$Factory.lambda$performHandshake$0] - Started new session 2325dacb5a5397552de3b69a52656fed (org.openqa.selenium.chrome.ChromeDriverService)
12:26:23.697 INFO [ActiveSessions$1.onStop] - Removing session 2325dacb5a5397552de3b69a52656fed (org.openqa.selenium.chrome.ChromeDriverService)

"nightwatch": "^0.9.20", "chromedriver": "^2.37.0", "selenium-server": "^3.11.0" "Chrome": 65.0 Mac OS Sierra 10.13.4

could you please tell me how to quit it? Thanks.

Upvotes: 4

Views: 786

Answers (1)

Lucas_Bo
Lucas_Bo

Reputation: 142

You can call the after method in each test like that: 

`'after' : function(browser, done) {
        browser.end(function(){
            done();
        });
    },

Begining of the actual Test: `

Upvotes: 1

Related Questions