DevOps Edition for Continuous Integration 10.4 | Unit Test Framework | Executing Tests | Continuous Integration | Configuring a Test Suite Executor
 
Configuring a Test Suite Executor
Software AG Designer allows you to configure Test Suite executor after you have successfully created the projects.
Perform the following steps to configure a sample test suite using the default files.
1. To initiate the tests, use the ant build file, run-composite-runner.xml and ant target, composite-runner-all-tests.
2. Modify the properties file, run-test-suites.properties to specify project locations and setting up target Integration Server definition.
3. Specify the following properties in the run-test-suites.properties file.
Name
Description
webMethods.integrationServer.name
Specifies the Integration Server host name.
For example: localhost, 27.0.0.1
webMethods.integrationServer.port
Specifies the Integration Server port.
For example: 5555
webMethods.integrationServer.userid
Specifies the Integration Server user name.
For example: Administrator, Developer
webMethods.integrationServer.password
Specifies the Integration Server user password.
For example: manage
webMethods.integrationServer.ssl
Specifies the Integration Server port uses SSL connection or normal.
For example: false or true
webMethods.home
Specifies the product installation location.
For example: C\:\\SoftwareAG
webMethods.test.setup.location
Specifies multiple project locations (absolute directory path) in $AbsoluteProjectLocation1,$AbsoluteProjectLocation2,$AbsoluteProjectLocation3 format. In this case, Test Suite Executor searches for all available and valid WmTestSuite files in these directories.
For example:
C:/SoftwareAG/IntegrationServer/instances/default/packages/SampleTestSuite,C:/_gitRepo/packages/SampleTestSuite1.
It executes specific and multiple WmTestSuite files by specifying it in the following format:$AbsoluteProjectLocation1;$RelativeTestSuitePath1,$AbsoluteProjectLocation2;$RelativeTestSuitePath2.
For example :
C:/SoftwareAG/IntegrationServer/instances/default/packages/SampleTestSuite;resources/test/setup/wmTestSuite.xml,C:/_gitRepo/packages/SampleTestSuite1;resources/test/setup/wmTestSuite.xml
webMethods.test.setup.external.classpath.layout
Specifies the relative paths within the projects where required classes or jar files are expected to be in Test Executor 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/
Note: Alternatively, you can also use the ant build file run-test-suites.xml and target runall-test. Test Suite Executor cleans and builds the projects included in target runall-test, then searches for the TestSuites and executes. List of projects can be included within runall-test target (under dirset contents). Reports are generated at the following default location: $basedir/test/reports. To use runall-test, the test projects or packages has to conform to the default project layout. Refer to the SampleTestSuite for the default project layout.
Copyright © 2017-2019 | Software AG, Darmstadt, Germany and/or Software AG USA, Inc., Reston, VA, USA, and/or its subsidiaries and/or its affiliates and/or their licensors.
Innovation Release