This document explains the end to end process of Test Management Option 2 in SAP Solution Manager, valid to 7.1 SP07.I have covered the process of exchange of business processes, business requirements, test assets and test results between SAP Solution Manager 7.1 and HP Quality Center 11,52. The type of test run I used is Manual run in the HP QC side; if we chose to automate the run then HP Quick Test Professional (now called HP UFT) can be used.
About HP Quality Center 11 as a part of HP ALM 11
The HP ALM platform provides the foundation for new versions of HP Quality Center and HP Performance Center, enabling application teams to manage the testing activities across the lifecycle, including monitoring the project status life cycle.
Source : SAP
SOLAR02 Business Requirement Transfer Process
The Business Blueprint Configuration (SOLAR02) is the single window for transferring the Blueprint from SAP side to Testing tool at the HP side. During the Blueprinting process of a project, the Business Scenarios and Processes are defined and all the possible variants for standard scenarios are identified. Once the configuration of a Business Process by Functional Consultants , including the Development, if any are done; the Blueprint can now be synced with the Testing tool for complete scenario testing. Business Process Document in a Documentation tab should be updated with the complete Process Flow. This plays a crucial role since the Tester working with HPQC might not be SAP Expert. So this document would be the basis for any reference during the testing process. We would take example of a Business Process “Procurement without QM” under Procurement scenario for our demo.
The Business Process document for this Process is maintained under Gen. Documentation tab in SOLAR02. This document comes along with the Business Process Structure when you define a business process from a Business Process Repository. Gen. Documentation tab is non editable, and only the standard documents provided by SAP as a reference would be available here. If you are configuring company specific (also known as Variant Business Process by functional folks) business processes, then Business Process Document should be maintained under Proj. Documentation tab manually.
Transfer to QC Tab
In the Transfer to QC Tab, two entities are maintained.
1. Business Requirement Document
Business Requirement Document, as mentioned above would be the *only* source of information for Testers to understand what the Business Process is all about. This document should provide information on “How” the Business Processes runs end to end and how to test the transactions involved in the business process. This document should also mention the expected results from the test run.The document maintained either Gen Document or Proj. Document would serve as a Requirement Document usually.
2. Test Object
Test Objects are Transaction Codes, Reports, Configurations or any relevant Developments which are part of your end to end Business Process. With the help of all the Test Objects you should be able to run your end to end Business Process. Hence select all the txn codes or reports involved in the business process here.
The sample tab would look like below;
Transferring the Blueprint data to HP ALM Tool
The Blueprint along with Test Objects and Test Requirements are transferred to HP Quality Center via the Dropdown “Send Data to Quality Center” option on the left corner of SOLAR02 screen.
Testing in HP Quality Center 11
In Requirements module, the process of translating the business requirements came from SAP Solution Manager into test requirements is done.To View the transferred Business Blueprint from Solution manager , proceed as below;
1. On the ALM sidebar, under Requirements, select Requirements.
2. Choose View > Requirements Tree to display requirements in a tree
You can use the requirements as a basis for defining your test plan tree in the Test Plan module. You can use the Convert to Tests wizard to assist you when designing your test plan tree. The wizard enables you to convert selected requirements or all requirements in the requirements tree to subjects or tests in the test plan tree. On the Business Process node, Right Click and select the option Convert to Test option
Select the second option, Convert lowest child requirements to tests, to convert the selected requirement to a subject folder, and its sub requirements to tests.
After you determine your testing goal, you build a test plan tree, which hierarchically divides your application into testing units, or subjects. For each subject in the test plan tree, you define tests that contain steps. For each test step, you specify the actions to be performed on your application and the expected
After you define a test set, select tests for inclusion in the test set. ALM adds instances of the selected tests to the test set. Each instance contains a defined test configuration.
When you run a test manually, you follow the test steps and perform operations on your application. Then, you compare the expected results with the actual outcome and record the results. You can execute a manual test as many times as needed. The results are stored separately for each run. If you use QTP/UFT as automation tool then this step is taken care by the QTP tool. You only have to click on the Run button and QTP agent will take care of running the entire test script.
Transfer the Result Back to SAP Solution Manager
The test results are transferred back to SOLAR02 to update the Blueprint with the testing information.
Test Results in SAP Solution Manager
There are two ways of displaying the test results in Solution Manager
1. Attribute option in SOLAR02
In the Transfer to QC tab in SOLAR02, the test results are displayed against each line item individually.
2. SOLAR_EVAL txn code
The entire view of test results are displayed in SOLAR_EVAL txn code as below