Conduct Integration Test

Use

The purpose of this task is to conduct the template integration test based on the template integration test plan. This is crucial for the functional verification of your template system. Participation of local project team members will aid in their understanding of the function of the template and its quality.

Template integration testing represents the testing of a chain of transactions that collectively represents a significant business process or scenario within your business environment. Integration testing also involves output documents, interfaces, procedures, organizational design and security profiles, and primarily focuses on representative business flows and high-impact business conditions. The purpose of the integration test is to ensure that mySAP.com solution fulfills your requirements and operates seamlessly across the various enterprise areas.

For Global ASAP, the testing of the Global Template may include selected functions that are "place holders" in the sense that local choices may provide another solution. Integration testing of the template needs to plan accordingly, and manage expectations appropriately when the template is rolled out and finalized as a productive local system.

Check the data conversion programs to verify that master and transactional data is correct and available for integration testing. Template integration testing is a critical milestone activity in your project.

Procedure

  1. Prepare for the Integration Test.
    Prepare test room, check equipment and system and collect relevant materials.
  2. Kick off the Integration Test.
    Introduce objectives and the plan to the test personnel. Ensure they all know the test logon procedure, and how to record issues.
  3. Enter initial setup data.
    Enter required setup data as defined in the Integration Test Procedure.
  4. Run test cases.
    Run each test procedure as defined in the Integration Test Plan.
  5. Record results.
    Record results in the "Actual Results" section on the Integration Test Procedure.
  6. Compare results to expected results.
    Compare Expected Results and Actual Results. Classify differences in terms of impact on the project. If you can, resolve the issue and re-test. Record other issues in the Issue Management System.
  7. Record issues.
    Record problems that you find during the test in the Issue Management System. Integration issues must be escalated and resolved quickly.
  8. Set test case as complete.
    Test Team Lead indicates when test case is complete on the Integration Test Case List.

Result

Also refer to the following documentation: