List of BW Maven Plugin Properties

Following properties are available from BW Maven Plugin 2.3.0

1. disableMocking

"disableMocking " is used to disable mocking for all mocked activities of BW Application.

Values:

 true:  Disable the mocking for all mocked activities from BW application.
 false: Enable the mocking for all mocked activities from BW application.

Example:

mvn test -DdisableMocking=true

This property can be used along with "test" and "site" goal

2. disableAssertions

"disableAssertions" is used to disable Assertions added for all activities of BW Application.

Values:

 true:  Assertions will not be run for all activities which are under unit testing from BW application.
 false: Assertions will be run for all activities which are under unit testing from BW application.

Example:

mvn test -DdisableAssertions=true

This property can be used along with "test" and "site" goal

3. showFailureDetails

"showFailureDetails" is used to show provided Input and Gold Input in case of Test Failure.

Values:

 true:  It will show the failure details in the console logs and BW execution report for the activities which are under unit testing from BW application.
 false: It will not show the failure details in the console logs and BW execution report for the activities which are under unit testing from BW application.

Example:

mvn test -DshowFailureDetails=true
mvn site -DshowFailureDetails=true

This property can be used along with "test" and "site" goal. Set to true by default from 2.7.1 onwards.

4. testSuiteName

"testSuiteName" is used to run the Test Suite.Provide the test suite name as a value to the property while running the "test" goal

Example:

mvn test -DtestSuiteName=%Test Suite Name%
mvn test -DtestSuiteName=ActivityAssertionTestSuite.bwts

User can Run mutiple test suite in sequence by proving the Test Suite names seperate by "/".

mvn test -DtestSuiteName=%TestSuiteName1%/%TestSuiteName2%
mvn test -DtestSuiteName=ActivityAssertionTestSuite.bwts/FaultTestSuite.bwts

This property can be used along with "test" and "site" goal

5. customArgEngine

"customArgEngine" property has been provided to pass the custom argument property file while starting the BW Engine. User needs to create a .properties file which will have the list of custom arguments in the form of -Dkey=value. The path of same .properties file needs to be passed to the "customArgEngine" property.

Example:

mvn test -DcustomArgEngine="D:\Issues\customArgEngine\sample.properties" where sample.properties file has the list of custom arguments.

The support has been provided for Absolute Path, Relative path and URL based file path.

Note: In case of relative path user need to keep properties file in Application Project.

6. skipInitMainProcessActivities

"skipInitMainProcessActivities" is used to skip init for all main process activities .

Values:

 true:  It will skip init for all main process activities.
 false: It will initiate the main process activities.

Example:

mvn test -DskipInitMainProcessActivities=true
mvn site -DskipInitMainProcessActivities=false

7. skipInitAllNonTestProcessActivities

"skipInitAllNonTestProcessActivities" is used to skip init for all non unit test process activities .

Values:

 true:  It will skip init for all non unit test process activities.
 false: It will initiate all non unit test process activities.

Example:

mvn test -DskipInitAllNonTestProcessActivities=true
mvn site -DskipInitAllNonTestProcessActivities=false

8. startOnDeploy

If user does not want to auto start application after deployment then this flag can be used. By default the value of "startOnDeploy" is "true"

Values:

 true:  It will auto start application after deployment.
 false: It won't auto start application after deployment.

Example:

mvn install-DstartOnDeploy=false

---

Please refer Troubleshooting page for more properties.