This topic applies only to the IBM Business Automation Workflow Advanced configuration.

Populating CVS with the required artifacts

Edit online
Draft comment:
This topic only applies to BAW, and is located in the BAW repository. Last updated on 2025-03-13 12:15
If you are using CVS as your team repository, you need to ensure that the repository contains the required artifacts to support batch processing of component test projects before you can build, deploy, and test the projects in a headless batch processing environment.

Before you begin

If your build.xml Ant script resides on a different machine than your CVS repository, you need to ensure that a CVS client is installed on the same machine as the build.xml Ant script. You can download and install a free CVS client from CVSNT.

About this task

To populate CVS with the required artifacts:

Procedure

  1. Ensure that your component test project does not include any SCA modules as utility JAR files. Component test projects can only contain libraries.
  2. Check your component test project into CVS.
  3. If your component test project has dependencies on WSDL, XSD, or Java™ interface files that are not contained in a library that is referenced by the component test project, complete the following steps:
    1. In the Business Integration view, expand your component test project. The WSDL, XSD, and Java interface files are automatically copied into the following source folder under the component test project (where ModuleName is the name of the associated module): ModuleNamedependencies
    2. Check the WSDL, XSD, and Java interface files into CVS.
    It is necessary to check the WSDL, XSD, and Java interface files into CVS because the component test project needs them at run time for the creation of the types required to run the tests. Checking these files into CVS enables you to work with the test artifacts without having the associated modules in the workspace.
  4. In the Physical Resources view, expand your component test project and check the generated Java class files for your test suites into CVS. Depending on whether you specified a folder for your test suites when you created them, the generated Java class files will have the following file names:
    • test.TestSuiteName.java
    • tablesFor_test.TestSuiteName_DataTable.java
    • FolderName.test.TestSuiteName.java
    • FolderName.tablesFor_test.TestSuiteName_DataTable.java
  5. Create a file to catalog your test suites by completing the following steps:
    1. In the workbench, run a search for the test suites in your component test project.
    2. Generate an XML file named TestSuiteList.xml that contains the names of the test suites and their corresponding class names and test cases.
    3. Check the TestSuiteList.xml file into CVS.
    You will need the information in the TestSuiteList.xml file to configure the scripts that perform the batch testing of your component test projects.