8. Deploying a Mark59 Selenium Script to JMeter

What is needed to run a Mark59 Selenium Script in JMeter

The requirements needed to execute a Mark59 selenium script in JMeter have been covered by the previous chapters, here we just 'put it all together'.

Please review:

So, depending on the build and how you set up the properties required by a Mark59 selenium script, there may are different combinations and locations of the files required.

For instance, the maximum number of artefacts required to be copied into a JMeter instance will occur when you need to use a Maven build producing the script jar with a separate library of dependencies, and place the WebDriver executable(s) within the JMeter file structure, and choose to use a mark59.properties file:

  • chromedriver.exe (Chrome WebDriver executable) in the JMeter bin directory

  • geckodriver.exe (Firefox WebDriver executable) in the JMeter bin directory

  • mark59.properties (with entries to the above drivers) in the JMeter bin directory

  • the script jar file in the JMeter lib/ext directory

  • the dependency directory for the script jar file in the JMeter lib/ext directory

The minimum number of artefacts required to be copied into a JMeter instance will occur when you use a Maven build producing a producing the script jar with dependencies included with the jar, and use system properties to define the location of the WebDriver executable(s) somewhere that is outside the JMeter instance:

  • the script jar file in the JMeter lib/ext directory

  • .... but you still need to have the WebDriver executable somewhere

For a single server test no changes are required to the existing JMeter properties or any other files, unless you chose to do so.

For distributed testing, you may need to set up SSL for RMI (the communication method the slave servers use to talk to the master server) . Refer to the JMeter User's Manual for details (this has nothing to do with Mark59, it's JMeter requirements for distributed testing). There are more details about distributed testing in the Continuous Integration chapter.