GreenPepper Maven Plugin - run

greenpepper:run

Run the specification testing.

Mojo Attributes

Requires a Maven 2.0 project to execute.
Requires dependency resolution of artifacts in scope: test
Automatically executes within the lifecycle phase: integration-test

Required Parameters

Name	Type	Description
fixtureOutputDirectory	File	The directory where compiled fixture classes go.
reportsDirectory	File	No description.
systemUnderDevelopment	String	The SystemUnderDevelopment class to use Default value is com.greenpepper.systemunderdevelopment.DefaultSystemUnderDevelopment

Optional Parameters

Name	Type	Description
debug	boolean	Set the Debug mode. Default value is false
excludeDefaultRunner	boolean	When launching the tests in a fork, we create a default runner. You can exclude this default runner from the testing process if you want to configure your owns.
fork	boolean	Launch the test in the Maven process if false. Or fork a java process if true. Default value is false
forkCount	Integer	The maximum number of default runner processes that needs to be spawn;
jvm	String	The Java Virtual Machine path to use for the default runner in fork mode.
locale	String	Set the locale for the execution.
refresh	boolean	Refresh the specificaction list (updating the index file) Default value is false
reportsType	SpecificationRunnerMojo$ReportType	The format of the generated reports. Can be html or xml. Default value is html
repositories	ArrayList	This list of repositories.
resume	boolean	Set this property to true to launch only new specifications + failed ones.
runners	List	The list of runners that can be associated to repositories for testing.
selectedRepository	String	Set this to a Repository name defined in the pom.xml. This option is only used in case `-Dgp.test` is used.
selector	String	Set the Selector class. Default value is com.greenpepper.document.GreenPepperInterpreterSelector
skip	boolean	Set this to 'true' to bypass greenpepper tests entirely. Its use is NOT RECOMMENDED, but quite convenient on occasion. Default value is false
specFilter	String	Sets a filter to filter the output of the specs. The filter should have a specific syntax: `"substring"` : a string to look for inside the page name. The search is case insensitive `"[RE]regular expression"` : a regular expression that will be used to match the page name Additionnally you can filter on the `implemented` status of the page by adding a `"[I]"` as a prefix to your search filter. `[I]` : Give the implemented pages only `[!I]` : Give the non implemented pages only Note: A `"[I]"` or `"[!I]"` as a search filter will filter only on the implemented status.\ Examples: `sun` : all specifications having the substring 'sun' `[RE]taurus` : the specification matching exactly 'taurus' `[I]` : all implemented specifications `[!I]` : all non implemented specifications `[!I]dummy` : all non implemented specifications having the substring 'dummy' `[I][RE]'.moon[^dab]+'` : all implemented specifications having the RE '.moon[^dab]+'
stopOnFirstFailure	boolean	Set this to 'true' to stop the execution on a failure. Default value is false
testFailureIgnore	boolean	Set this to true to ignore a failure during testing. Its use is NOT RECOMMENDED, but quite convenient on occasion.
testSpecification	String	Set this to a Specification name to run only this test. The test is searched inside the default repository.
testSpecificationOutput	String	Set this to a Specification name to run only this test. The test is searched inside the default repository.

Parameter Details

debug

Set the Debug mode.

Type	boolean
Required	No
Expression	${maven.greenpepper.debug}
Default	false

excludeDefaultRunner

When launching the tests in a fork, we create a default runner. You can exclude this default runner from the
testing process if you want to configure your owns.

Type	boolean
Required	No
Expression	${maven.greenpepper.excludedefaultrunner}

fixtureOutputDirectory

The directory where compiled fixture classes go.

Type	java.io.File
Required	Yes
Expression	${project.build.directory}/fixture-test-classes

fork

Launch the test in the Maven process if false. Or fork a java process if true.

Type	boolean
Required	No
Expression	${maven.greenpepper.fork}
Default	false

forkCount

The maximum number of default runner processes that needs to be spawn;

Type	java.lang.Integer
Required	No
Expression	${maven.greenpepper.forkcount}

jvm

The Java Virtual Machine path to use for the default runner in fork mode.

Type	java.lang.String
Required	No
Expression	${maven.greenpepper.jvm}

locale

Set the locale for the execution.

Type	java.lang.String
Required	No
Expression	${maven.greenpepper.locale}

refresh

Refresh the specificaction list (updating the index file)

Type	boolean
Required	No
Expression	${greenpepper.refresh}
Default	false

reportsDirectory

No Description.

Type	java.io.File
Required	Yes
Expression	${project.build.directory}/greenpepper-reports

reportsType

The format of the generated reports. Can be html or xml.

Type	com.greenpepper.maven.plugin.SpecificationRunnerMojo$ReportType
Required	No
Expression	${maven.greenpepper.reports.type}
Default	html

repositories

This list of repositories.

Type	java.util.ArrayList
Required	No

resume

Set this property to true to launch only new specifications + failed ones.

Type	boolean
Required	No
Expression	${maven.greenpepper.resume}

runners

The list of runners that can be associated to repositories for testing.

Type	java.util.List
Required	No

selectedRepository

Set this to a Repository name defined in the pom.xml.
This option is only used in case -Dgp.test is used.

Type	java.lang.String
Required	No
Expression	${gp.repo}

selector

Set the Selector class.

Type	java.lang.String
Required	No
Expression	${maven.greenpepper.selector}
Default	com.greenpepper.document.GreenPepperInterpreterSelector

skip

Set this to 'true' to bypass greenpepper tests entirely.
Its use is NOT RECOMMENDED, but quite convenient on occasion.

Type	boolean
Required	No
Expression	${maven.greenpepper.test.skip}
Default	false

specFilter

Sets a filter to filter the output of the specs. The filter should have a specific syntax:

"substring" : a string to look for inside the page name. The search is case insensitive
"[RE]regular expression" : a regular expression that will be used to match the page name

Additionnally you can filter on the implemented status of the page by adding a "[I]"
as a prefix to your search filter.

[I] : Give the implemented pages only
[!I] : Give the non implemented pages only

Note: A "[I]" or "[!I]" as a search filter will filter only on the implemented status.\
Examples:

sun : all specifications having the substring 'sun'
[RE]taurus : the specification matching exactly 'taurus'
[I] : all implemented specifications
[!I] : all non implemented specifications
[!I]dummy : all non implemented specifications having the substring 'dummy'
[I][RE]'.*moon[^dab]+' : all implemented specifications having the RE '.*moon[^dab]+'

Type	java.lang.String
Required	No
Expression	${gp.specFilter}

stopOnFirstFailure

Set this to 'true' to stop the execution on a failure.

Type	boolean
Required	No
Expression	${maven.greenpepper.test.stop}
Default	false

systemUnderDevelopment

The SystemUnderDevelopment class to use

Type	java.lang.String
Required	Yes
Default	com.greenpepper.systemunderdevelopment.DefaultSystemUnderDevelopment

testFailureIgnore

Set this to true to ignore a failure during testing.
Its use is NOT RECOMMENDED, but quite convenient on occasion.

Type	boolean
Required	No
Expression	${maven.greenpepper.test.failure.ignore}

testSpecification

Set this to a Specification name to run only this test.
The test is searched inside the default repository.

Type	java.lang.String
Required	No
Expression	${gp.test}

testSpecificationOutput

Set this to a Specification name to run only this test.
The test is searched inside the default repository.

Type	java.lang.String
Required	No
Expression	${gp.testOutput}