Page History

This topic explains how SOAtest test cases can be mapped to specific requirements in HP ALM / Quality Center. Once a test case is mapped to a requirement, the testing of the requirement becomes as simple as clicking a button inside HP ALM. Parasoft test cases can then be run from inside HP ALM and the results will be reported back to HP ALM.

...

1. Extract the contents of the ZIP file that is shipped <SOAtest Installation>/integration/HP to (deprecated) to the folder <HP Deployment ocation>\application\20qcbin.war. Refer to the HP ALM Installation Guide for the HP Deployment Location (on Windows Server 2003, it is
   C:\Documents and Settings\All Users\Application Data\HP\ALM).

2. Run the HP Server Deployment Wizard. This redeploys HP ALM with the necessary test type updates.
3. Using IE with Administrator privileges, log in to HP ALM as Site Administration, then select Tools> Update Test Types. This will make the custom test type available for use in the active projects.
4. Log out of HP ALM.

...

1. Create a temporary scratch directory on the Quality Center server machine. You can create the scratch directory in the Quality Center application directory (for example, C:\Program Files\HP\Quality Center\application\my_scratch_files).
2. Go to Quality Center’s jboss\server\default\deploy directory and copy the 20qcbin.war file to your scratch directory.
3. Go to your SOAtest installation’s integration\HP (deprecated) directory (for example, C:\Program Files\Parasoft\SOAtest\<version>\integration\HPHP (deprecated)) and copy the soatest_test_type.zip file to your scratch directory on the Quality Center server.
4. Unzip soatest_test_type.zip into your scratch directory. This should create two folders: CustomTestTypes and Extensions.

5. Update 20wcbin.war with CustomTestTypes and Extensions. You can do this using the jar command from the Java JDK. For example, you might use 
   jar uvf 20qcbin.war CustomTestTypes Extensions
   Since war files use the zip file format, a zip application could also be used to update 20qcbin.war.

6. Make a backup copy of the original 20qcbin.war file in the jboss\server\default\deploy directory—for instance, you could copy the original file, then rename it to 20qcbin.war.bak.
7. Copy the new 20qcbin.war file from your scratch directory to the jboss\server\default\deploy directory.
8. Restart Quality Center. Typically you would do this from the Windows Services console (e.g., by choosing Start> Administrative Tools> Services).
9. Add Parasoft SOAtest to the list of test type options.
   1. Open a browser and enter the URL http://<server:port>/qcbin/start_a.htm
   2. Click the HP Quality Center link.
   3. Log on to Quality Center
   4. Click Tools> Customize.
   5. Click Project Entities.
   6. Expand Test then expand System Fields.
   7. Select Type then click the Goto List button.
   8. Click the New Item button, enter Parasoft SOAtest for the item name, then click OK.
   9. Close the Project Lists box then click Save.
   10. Log out of Quality Center. The changes will then take effect.

...

1. After logging in to ALM, select the Test Plan module. The Test Plan module allows you to set up your automated test and custom scripts.
2. In the Test Plan Tree, select Subject and click the New Folder toolbar button.
   
   
   
   
3. In the New Folder dialog box, enter a folder name (e.g., SOAtest) in the Test Folder Name field.
   
   
   
   
4. Select the newly-created folder, then click the New Test icon from the above toolbar.
   
   
   
   
5. In the Create New Test dialog box, select VAPI-XP-TEST in the Test Type drop-down box, enter a test name (e.g., SOAtest Demo) in the Test Name field, then click OK.
   
    
   
   
6. In the HP VAPI-XP Wizard select JavaScript as the Script Language, enter SOAtest for Script Name, then click Finish.
7. Open the Test Script tab. Notice that a template has been created from the HP VAPI-XP wizard.
   
   
   
   
8. Open the customized SOAtest script HPQualityCenter.txt located in integration/HP (deprecated) within the SOAtest install directory.
   
   Note that the script assumes the default install location is c:/Progra~1/Parasoft/SOAtest/[SOAtest version number]/. The script is configured to run a test suite called HPQuality-Center.tst within the examples/tests directory. 
9. Copy the HPQualityCenter.txt script and replace it in the template.
   
   
   
   
10. Modify the script as needed (see the following section for details).
11. Save the script.

...

The HPQualityCenter.txt integration script  (located in integration/HP (deprecated) within the SOAtest installation directory) is used in your test's Test Script tab in order to tell SOAtest to run your project file and report the test results back to HP ALM / QC. 

...