Running NeoLoad
< Prev Chapter 2. Installation Next >

Running NeoLoad

Running the Controller

Running the graphical interface

Windows: <install_dir>\bin\NeoLoadGUI.exe.

Unix: <install_dir>/bin/NeoLoadGUI.

Running from the command line

Windows: Use N<install_dir>\bin\NeoLoadCmd.exe for command line options.

Unix: Use <install_dir>/bin/NeoLoadCmd for command line options.

Command line options:

syntax: neoloadCmd -project <file> -launch <scenario> [-report <file>] [-noGUI]
-project  use the specified project (*.nlp)
-launch   run the test using the specified scenario        
-report   generate an end of test report. NeoLoad will output the report
          in the format specified by the extension
          (.html, .pdf, .xml)
-noGUI    run NeoLoad without the GUI (Graphical User Interface)
-exit     close NeoLoad when the test has finished
          (this option is taken in account only when the GUI is displayed,
          NeoLoad always exits when no GUI is displayed)
-help     help with the options

Note that relative paths are relative to the NeoLoad directory.

Sample

neoloadCmd -project projects/jpetstore/jpetstore.nlp -launch scenario1
-noGUI -report projects/jpetstore/reports/report.xml

Using NeoLoad with ANT

Integrating NeoLoad with your ANT script is easy. Just use the NeoLoad task provided in <install_dir>/lib/ant-neoload.jar. To make the NeoLoad task available to ANT, you must first insert a taskdef element to tell ANT where to find the task definition. Here is an example of using the task in an ANT build file:

<taskdef name="neoload"
   classname="com.neotys.nl.ant.NeoLoad"
   classpath="${NEOLOAD.install.dir}/lib/ant-neoload.jar" /> 

<neoload
   projectFile="projects/jpetstore/jpetstore.nlp" 
   scenarioname="scenario1"
   showgui="false" 
   report="projects/jpetstore/reports/report.xml"
   exit="true"
/>

Note that relative paths are relative to the NeoLoad directory.

The taskdef definition must occur only once in each ANT build file and can appear anywhere on the top level, below the project element. If you move the ant-neoload.jar archive to another location, then you must specify the location of the NeoLoad command line executable using the controllerExecutable parameter.

Parameters:

  • projectFile - mandatory - the project file (*.nlp).

  • scenarioname - mandatory - the scenario name.

  • showgui - optional - if true, shows the graphical interface during the test. Default value is false.

  • report - optional - generate an end of test report. NeoLoad will output the report in the format specified by the extension (.html, .pdf, .xml)

  • controllerExecutable - optional - path to the NeoLoad executable (<install_dir>/bin/NeoLoadCmd.exe). This parameter is optional if you pick the ant-neoload.jar archive from the NeoLoad installation directory. The parameter is mandatory if you move the archive to another directory.

Running the Load Generator

For each test, the Load Generator is started by an Agent. The Load Generator must always be started by an Agent, never run directly:

Windows:

  • As a service: start/stop NeoLoad Agent in the Windows Services control panel.

  • Manually: start using <install_dir>\bin\Agent.exe; stop the Agent by clicking on the system tray icon.

Unix:

  • Start the Agent with <install_dir>/bin/AgentService start and stop it with <install_dir>/bin/AgentService stop.

< Prev Up Next >
License Key Management Home Advanced Installation