Versions Compared

Version Old Version 13 New Version 14
Changes made by

Sebastian Letzel

Sebastian Letzel

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Code Block
languagejava
java -cp greenpepper-core-X.X.X-all.jar;path/to/systemundertest/classes;path/to/systemunderdevelopment/classes; com.greenpepper.runner.Main -s /path/to/myspecs /path/to/outputresults

Configuration

Any of the rules above can be overridden using command line switches.GreenPepper CommandLineConfiguration

Arguments

Invoking the command line interface with the --help option brings up the usual help message:

Panel
bgColorlightgrey
borderStyledashed
Usage: greenpepper [options] input [ouput]
Run the input specification and produce a report in output file or in directory specified by -o

Options:
    --lazy                    Execute document in lazy mode
-l, --locale LANG             Set application language (en, fr, ...)
-f, --sud CLASS;ARGS          Use CLASS as the system under development and instantiate it with ARGS
-o DIRECTORY                  Produce reports in DIRECTORY (defaults to current directory)
-r CLASS;ARGS                 Use CLASS as the document repository and instantiate it with ARGS (defaults to com.greenpepper.repository.FileSystemRepository)
    --selector CLASS          Use CLASS as the interpreter selector (defaults to com.greenpepper.document.GreenPepperInterpreterSelector)
-s, --suite                   Run a suite rather than a single test (output must refer to a directory)
-t SECTIONS                   Filter input specification to only execute SECTIONS (comma separated list of sections)
    --xml                     Generate XML report (defaults to plain)
    --help                    Display this help and exit
    --version                 Output version information and exit
    --debug                   Enable debug mode
    --stop                    Stop the execution of the specification on the first failure

 

Default options

When no option is given, Image Removed defaults to the following rules:

  • Input is a single specification, not a suite
  • If output is not specified, reports are produced in the current directory
  • Report is in plain format
  • The operating system locale is used
  • The input specification is not filtered
  • The specification file must be located on the file system
  • Fixtures are created using the default built-in mechanism
  • Tables use Image Removed formalism
  • Lazy mode is disabled
  • Debug mode is disabled
  • Will not stop the execution on first failure

Commandline Configuration

How to deal with static fixture fields and the programmatically execution?

...