Skip to main content
Software Quality Assurance & Testing

Return to Answer

replaced http://stackoverflow.com/ with https://stackoverflow.com/
Source Link
Community Bot
Community Bot
  • 1

I would setup a Jenkins free-style job and execute the java based Se Interpreter from a shell-script task

  1. Setup free-style Jenkins build
  2. Schedule build with github with the git-plugin to run job on each commit
  3. Add a shell-script that runs the Se Interpeter in the build and make sure it has a correct exit code to fail/success the run or see this questionsee this question for options.

Shell script would look something like this:

java -jar SeInterpreter.jar --driver=Remote --driver.browserName=firefox --driver.url=http://selenium_grid.local/wd/hub/ tests.json

  1. Setup a Selenium Grid hub and nodes or use the Jenkins SE Grid plugin (which setups each Jenkins node as grid node, but you need to make sure the browsers can start on the Jenkins machines.) to run the tests against.

I would prefer a separate grid or even better run against SauceLabs or TestingBot, since maintaining your own Grid could become cumbersome pretty soon.

There is also a node.js version of the Se Interpreter, which might be interesting for people running a JavaScript stack.

I would setup a Jenkins free-style job and execute the java based Se Interpreter from a shell-script task

  1. Setup free-style Jenkins build
  2. Schedule build with github with the git-plugin to run job on each commit
  3. Add a shell-script that runs the Se Interpeter in the build and make sure it has a correct exit code to fail/success the run or see this question for options.

Shell script would look something like this:

java -jar SeInterpreter.jar --driver=Remote --driver.browserName=firefox --driver.url=http://selenium_grid.local/wd/hub/ tests.json

  1. Setup a Selenium Grid hub and nodes or use the Jenkins SE Grid plugin (which setups each Jenkins node as grid node, but you need to make sure the browsers can start on the Jenkins machines.) to run the tests against.

I would prefer a separate grid or even better run against SauceLabs or TestingBot, since maintaining your own Grid could become cumbersome pretty soon.

There is also a node.js version of the Se Interpreter, which might be interesting for people running a JavaScript stack.

I would setup a Jenkins free-style job and execute the java based Se Interpreter from a shell-script task

  1. Setup free-style Jenkins build
  2. Schedule build with github with the git-plugin to run job on each commit
  3. Add a shell-script that runs the Se Interpeter in the build and make sure it has a correct exit code to fail/success the run or see this question for options.

Shell script would look something like this:

java -jar SeInterpreter.jar --driver=Remote --driver.browserName=firefox --driver.url=http://selenium_grid.local/wd/hub/ tests.json

  1. Setup a Selenium Grid hub and nodes or use the Jenkins SE Grid plugin (which setups each Jenkins node as grid node, but you need to make sure the browsers can start on the Jenkins machines.) to run the tests against.

I would prefer a separate grid or even better run against SauceLabs or TestingBot, since maintaining your own Grid could become cumbersome pretty soon.

There is also a node.js version of the Se Interpreter, which might be interesting for people running a JavaScript stack.

Source Link
Niels van Reijmersdal
Niels van Reijmersdal
  • 32.6k
  • 4
  • 59
  • 125

I would setup a Jenkins free-style job and execute the java based Se Interpreter from a shell-script task

  1. Setup free-style Jenkins build
  2. Schedule build with github with the git-plugin to run job on each commit
  3. Add a shell-script that runs the Se Interpeter in the build and make sure it has a correct exit code to fail/success the run or see this question for options.

Shell script would look something like this:

java -jar SeInterpreter.jar --driver=Remote --driver.browserName=firefox --driver.url=http://selenium_grid.local/wd/hub/ tests.json

  1. Setup a Selenium Grid hub and nodes or use the Jenkins SE Grid plugin (which setups each Jenkins node as grid node, but you need to make sure the browsers can start on the Jenkins machines.) to run the tests against.

I would prefer a separate grid or even better run against SauceLabs or TestingBot, since maintaining your own Grid could become cumbersome pretty soon.

There is also a node.js version of the Se Interpreter, which might be interesting for people running a JavaScript stack.