GreenPepper Server is packaged with the latest GreenPepper Core runner. (Test engione)
But you might in the future, need to add another Runner or customize an existing one.

These screens are accessible from: Confluence's space admin OR JIRA's GreenPepper Config tab

I. Add a new Runner

  To add a Custom Runner to your GreenPepper Server available runner list please follow these steps.

1. Click on Add a new Runner
   
   
   
   
   
2. Enter the name of your Runner (Mandatory)
3. Enter the Command line (please refer to Executing a Specification)
   Know that (similar to velocity)
   • ${classpaths} will be replaced by the Runner, SUT and Fixtures classpaths -(Mandatory for GP)
   • ${mainClass} will be replaced by the Runner specified Main Class -(Mandatory for GP)
   • ${inputPath} will be replaced by an input path -(Mandatory for GP)
   • ${outputPath} will be replaced by an output path -(Mandatory for GP)
   • ${locale} will be replaced by the user locale -Default: English (java only)
   • ${repository} will be replace by the repository of the Specification resolver class -Default: FileSystemRepository
   • ${fixtureFactory} will be replaced by the SUT Fixture Factory Class;Fixture Factory Args -Default: CoreFixtureFactory
     

Example of a JAVA command line:
java -mx252m -cp ${classpaths} ${mainClass} ${inputPath} ${outputPath} -l ${locale} -r ${repository} -f ${fixtureFactory} --xml
Example of a .Net command line:
c:/dotnet/GreenPepper.exe -a ${classpaths} ${mainClass} ${inputPath} ${outputPath} -r ${repository} -f ${fixtureFactory} --xml

1. The Server name and port (if you are using the Remote agent)
   
   
   
   
   
2. Click Save
3. Enter the location of your Runner library and its dependencies.
   
   
   

II. Edit an existing Runner

To customize an existing Runner of your GreenPepper Server available runner list please follow these steps.

1. Select the Runner to update
2. Click ont the edit next to your selection.
   
   
   
   
   
3. Edit the new values.
4. Click Save next to your selection
   
   

   Constraints The Runner Name must be Unique. You may not remove a Runner associated with existing System Under Test.