System Requirements

The following are the system requirements for the TestPartner integration:
• TestPartner version 6.3.
• SilkCentral Test Manager Version 2009 SP1.
• A SilkCentral 2009 SP1 Execution Server must be installed on the on the machine where you wish to run the TestPartner scripts.


Known Issues

There a couple of known issues with this plug-in and they are detailed below.

• Source Control Profiles

If the port number provided does not match the database type, the Source Control Profile window may hang.
Double check that the database type is correct before clicking OK.

• Error Message

If you run the TestPartner integration and you get a message similar to

javax.xml.transform.TransformerFactoryConfigurationError:
Provider org.apache.xalan.processor.TransformerFactoryImpl not found

Do one of the following:
• Copy xalan.jar from a /lib to /lib.
• Or, do not use the Standalone Execution Server setup to install the SilkCentral Execution Server and instead use the full SilkCentral Test Manager setup, and select Execution Server Installation on the Setup Type page.

• TestPartner with Oracle Database

When connecting to a TestPartner Oracle database, there is a TestPartner requirement that the TNS name must be the same as the host server name.


Installing the TestPartner Plug-in

1. Download the SCTM_TestPartner_Plug-in_WS1.zip integration ZIP file from the TestPartner section of the Product Updates page on http://supportline.microfocus.com.
2. Open SCTM_TestPartner_Plug-in_WS1.zip. It contains two additional ZIP files: TestPartner.zip and TestPartnerDB.zip. These two files should be extracted from SCTM_TestPartner_Plug-in_WS1.zip but they should not be opened themselves. Copy both files into the plugins directory of the SilkCentral Test Manager installation directory on the application server:

C:\Program Files\Silk\SC Test Manager 2009\Plugins\TestPartner.zip
C:\Program Files\Silk\SC Test Manager 2009\Plugins\TestPartnerDB.zip

3. Right-click on the SilkCentral Service Manager icon in the Taskbar.



4. Select “Stop All Services” and wait until the red rectangle on the icon becomes a complete red square.



5. Then right-click on the icon again and select “Start All Services”.
6. You will also need to ensure that the SilkCentral Execution Server service is not running on the machine where you wish to run the TestPartner scripts. You should have the SilkCentral Execution Server process running instead. To do this follow these instructions:

• Open the SilkCentral Service Manager window by right-clicking on the icon in the Taskbar and selecting “Open Service Manager”.



• Click the SilkCentral Execution Server tab.
• If running, click Stop and ensure that Run at startup is not checked.
• Click the Execution Server (Process) tab.



• If not running, click Start and ensure that Run at startup is checked.


Using TestPartner with SilkCentral Test Manager

Creating a TestPartner Source Control Profile

1. Create a new project or open an existing project in SilkCentral Test Manager.
2. Click Settings on the Test Manager workflow bar.
3. Click the Source Control tab to open the Source Control Profiles page.
4. Click New Profile.
    • The New Source Control Profile dialog box displays.
5. Type a name in the Name text box.
6. Select TestPartner from the Source control system list box.
7. Select a database type from the Database type list box, either SQL Server or Oracle.
8. Enter the name of the TestPartner database server in the Database server text box.
9. Enter the name of the TestPartner database in the Database name text box.
10. Enter the port number of the TestPartner database server in the Database port text box.
11. Enter the TestPartner database schema or owner name in the Database schema/owner name text box.
12. Enter the name of the database user in the Database user text box.
13. Enter the password for the database user in the Database password text box.
14. Enter the name of a valid TestPartner user in the TestPartner user name text box.
15. Enter the password for the TestPartner user in the TestPartner password text box.
16. Enter the Working folder to which the Test Manager Execution server should copy the source files.
    • The working folder must be a local path. For example, C:\TempSources\.
17. Use the Project path text box to filter which scripts from the database are available to use as tests.
18. Click Browse.
    • The Select Project Path dialog box opens.



19. Select a level from the list below. These will be the scripts that you are able to select within the source control profile:
    • First level - this is the TestPartner database.
        • Note: If you select this level, the Project path text box will be blank.
    • Second level - this is the TestPartner project.
    • Third level - this is the script type within a specified TestPartner project.
20. Click OK. The path will be added to the Project path text box.



21. Click OK to save the source control profile.




Creating a TestPartner Test Container

1. Click Test Plan on the Test Manager Workflow bar.
2. Click New Test Container on the toolbar (or right-click within the tree view and choose New Test Container).
    • The New Test Container dialog box will display.
3. Define a Name (or accept the default name) and a Description for the container.
    • Note: SilkCentral Test Manager supports HTML formatting and cutting and pasting of HTML content for Description fields.
4. Select any pre-defined Product that is to be associated with this test container from the list box.
    • See SilkCentral Test Manager Administration Module Help for details regarding adding product profiles.
5. Select a source control profile that uses TestPartner from the Source Control Profile list box.
    • Note: Defining source control profiles allows you to define where SilkCentral Test Manager’s execution servers should retrieve program sources for test execution. See SilkCentral Test Manager Administration Module Help for details regarding source control settings.
6. Use the Root Node text box and Browse button to override the path defined in the source control profile.
    • Otherwise, leave it blank.
7. Ignore the subsequent text boxes as they do not apply to a TestPartner test container.



8. Click OK.


Creating a TestPartner Test Definition

1. Click Test Plan on the Test Manager workflow bar.
2. Select a container or folder node in the Test Plan tree where you want to insert a new test definition.
3. Click New Test Definition on the toolbar or right-click within the tree and choose New Test Definition.
    • The Test Definition dialog box opens.
4. Specify a name and description for the test definition.
    • Note: SilkCentral Test Manager supports HTML formatting as well as the cutting and pasting of HTML content for text boxes.
5. Select TestPartner Test from the Type list box.
    • Note: Throughout the test-definition configuration process and across all test definition types, Inherit from parent check box options are provided where applicable, enabling you to accept settings of any existing parent entity.



6. Click Next.
    • The TestPartner Test Properties dialog box opens.
7. Click Browse next to the Script Name text box.
    • The Choose File dialog box opens. The assets available in this dialog box are based on the Project Path defined in the associated TestPartner source control profile. Select a script from the list and click OK.



8. Enter a TestPartner playback option in the Playback Options text box.



9. Click Finish.




Running a TestPartner Test

In order to run the created Test Definition you will need to create an Execution Definition in the usual manner. You will then need to assign the TestPartner Test Definition to this Execution Definition and deploy it to the relevant Execution environment (machine on which you wish to run the Test Partner script). You can then run the Execution Definition in the usual manner. If you need more information on creating or running Execution Definition then you should refer to the SCTM online help.


Viewing the TestPartner Result File

1. Click Test Plan on the Test Manager Workflow bar.
2. Expand the test container containing the test from which you want to view the results.
3. Click Runs.



4. Each of the test definition runs displays in the list.
5. In the Run ID column, select the run that you want to view.
6. The Test Definition Run Results window displays.



7. Click Files.



8. The TestPartner result file displays in the list.
9. Click details.htm to view the TestPartner result file.



10. Click the “Back” on your Browser to close the result file.