Designer 10.15 | webMethods Unit Test Framework Help | Executing Tests | Continuous Integration | Configuring a Test Suite Executor | Project Information
 
Project Information
webMethods.home
Specifies the product installation location.
For example:
C:\SoftwareAG
webMethods.test.setup.location
Specifies multiple project locations (absolute directory path) in the following format. In this case, a Test Suite Executor searches for all available and valid Test Suite files in these directories.

$AbsoluteProjectLocation1,
$AbsoluteProjectLocation2,\
$AbsoluteProjectLocation3
For example:
C:/SoftwareAG/IntegrationServer/instances/default/packages/SampleTestSuite,\
C:/_gitRepo/packages/SampleTestSuite1
If you want to execute a specific and multiple Test Suite files, specify the absolute directory path in the following format.
$AbsoluteProjectLocation1;$RelativeTestSuitePath1,\
$AbsoluteProjectLocation2;$RelativeTestSuitePath2
For example:
C:/SoftwareAG/IntegrationServer/packages/SampleTestSuite;resources/test/setup/wmTestSuite.xml,\
C:/_gitRepo/packages/SampleTestSuite1;resources/test/setup/wmTestSuite.xml
Alternatively, you can declare values for this property by referencing a file containing the actual data, which helps improve the formatting of the run-test-suites.properties file when providing large values.
The format for declaring values is as follows:
webMethods.test.setup.location=reference\:file\:project-locations.properties 
where project-locations.properties is the file that contains a list of project locations.
For example:
webMethods.test.setup.location=\
C:/SoftwareAG/IntegrationServer/instances/default/packages/SampleTestSuite,\
C:/_gitRepo/packages/SampleTestSuite1
webMethods.test.setup.external.classpath.layout
Specifies the relative paths within the projects where the required classes or jar files are expected to be present in a Test Suite Executor project build-classpath. For example, when third-party libraries or Mockfactory classes are referred from the Tests, specify the locations where these are stored at, so that executor can load these dependencies during headless tests. Append the default comma separated list if required.
Default value:
resources/test/classes,resources/java/classes,resources/test/jars,
resources/java/jars,resources/jars
webMethods.test.profile.result.location
Specifies the absolute directory location where the reports are stored.
For example:
C:/git_sources/GitRepo3/WmTestSuiteExecutor/test/reports/
Important:
It is recommended not to customize the code coverage report resources and the Ant build file artifacts of the Test Suite Executor project directly, Instead:
*Import the available Ant targets in use to any new Ant build files and reuse them, which prevents any conflicts during the migration of the Test Suite Executor project artifacts to the latest fixes or new releases.
*Keep the Test Suite Executor artifacts in sync with the fix or release version of the product in use to avoid compatibility issues.
*Recreate the Test Suite Executor project in Designer, which distributes compatible resources.