Skip to content

Latest commit

 

History

History
72 lines (54 loc) · 1.83 KB

README.md

File metadata and controls

72 lines (54 loc) · 1.83 KB
Raw

grunt-selenium-server

Start/stop a local Selenium standalon server.

Getting Started

npm install grunt-selenium-server --save-dev
grunt.loadNpmTasks('grunt-selenium-server');

Grunt config example:

'selenium-server-start': {
  dev: {

  }
},
'selenium-server-stop': {
  dev: {

  }
}

Grunt task example:

grunt.registerTask('devUI', 'run selenium server and phpunit', function(){
   grunt.task.run(['start-selenium-server:dev', 'phpunit:dev', 'stop-selenium-server:dev']);
});

Run:

grunt devUI

Kill selenium in case your grunt tasks fails before we reach 'stop-selenium-server':

        var seleniumChildProcesses = {};
        grunt.event.on('selenium.start', function(target, process){
            grunt.log.ok('Saw process for target: ' +  target);
            seleniumChildProcesses[target] = process;
        });

        grunt.util.hooker.hook(grunt.fail, function(){
            // Clean up selenium if we left it running after a failure.
            grunt.log.writeln('Attempting to clean up running selenium server.');
            for(var target in seleniumChildProcesses) {
                grunt.log.ok('Killing selenium target: ' + target);
                try {
                    seleniumChildProcesses[target].kill('SIGTERM');
                }
                catch(e) {
                    grunt.log.warn('Unable to stop selenium target: ' + target);
                }
            }
        });

Notes:

  1. If you won't handle this event, if your phpunit (for example) will fail the selenium server process will remain active in the background.

  2. The "grunt.fail" event will be fired whenever any grunt task is failing. Thus you might want to consider using a more specific event related to the task that actually uses selenium server. i.e phpunit in the above example.