Enterprise Resource Planning Blogs by Members
Gain new perspectives and knowledge about enterprise resource planning in blog posts from community members. Share your own comments and ERP insights today!
cancel
Showing results for 
Search instead for 
Did you mean: 
former_member571
Explorer
SAP S/4HANA Testing

SAP S/4HANA testing is based on on-premise activities and testing tools that are different from the two cloud solutions. With the Transition to SAP S/4HANA implementation roadmap, there are three scenarios that can occur for a project deployment:

  1. New implementation

  2. System conversion

  3. Selective data transition.


We’ll focus on the on-premise guidance in this section and walk you through the
Testing workstream in the explore and realize phases.

The Testing workstream begins with the test planning activities that occur in the
explore phase.

The main activities include the following:

> Familiarizing yourself with the tools in test management
> Setting up test management in SAP Solution Manager
> Determining the test scope
> Performing detailed test planning

It’s strongly encouraged to finalize the planning for testing as early as possible and
outline and identify the project scope, testing objectives and assumptions, types of
testing, approach, tools, defect management, and roles and responsibilities of the
testing team to minimize the number of risks and issues going forward. Having a
solid ground for these key elements sets the road for smoother testing activities and
milestones for the project deployment

Teams must understand the test tools in test management and the setup of SAP Solution Manager as these will be used heavily during multiple key events. Multiple resources are available to the project team to fully familiarize themselves with the testing learning journey (see Figure 5.12). If you’re using SAP Model Company, the technical activation of SAP Model Company is explained in a handover workshop that is part of the SAP Model Company package. The procedures differ per SAP Model Company. SAP Value Assurance and SAP Model Company nicely fit with each other.


Figure 5.12 SAP Solution Manager Test Suite Overview

Next, the scope of testing for a project, regardless of whether the project is executed independently or as part of a release, needs to be determined early to ensure the testing environments and materials are available for execution.

With such a variety of testing cycles available (e.g., integration, regression, performance, cutover, and UAT), it’s important to define the cycles that are required to support the planned conversion event.

The last activity, which closes out the explore phase, is detailed test planning.

This is where the scoping and planning of the test is required for the transition project to determine which testing cycles are required to meet the quality gate conditions for entering the realize phase.

This includes evaluating and enabling test management and the test automation tools to support the testing activities across milestones, as well as executing tasks using application lifecycle management (ALM) best practices for test management and tailoring the templates for the test strategy and functional test plan to meet the project team needs. In addition, the detailed testing plan should support the need to mitigate risks that may arise for the end-state solution and during cutover activities.

The last phase in the Testing workstream for the Transition to SAP S/4HANA implementation roadmap encompasses the following:

> Execution plan for the realize phase

> Test preparation

> Test execution

 

Let’s take a dive into these last three key components of the Testing workstream.

The purpose of the execution plan for the realize phase is to execute the work defined, manage the sprints/testing as defined previously, log all issues, and document them in the system for traceability.

Furthermore, the project team manages the integration, security, and UAT.

Next, the test preparation task and objective is to prepare all business-process-related tests according to customer-specific configurations.

Preparing the tests is based on determining the evaluation of the existing test materials, which were identified in the explore phase (i.e., testing plan), and other assets for execution of the testing cycles.

Any missed test materials and test scripts that are realized must be developed in accordance with the detailed test plan to capture all testing-critical materials and documentation. Testing teams can leverage the fully ready and detailed test scripts, process flows, and other documentation via SAP Best Practices Explorer.

SAP Best Practices Explorer provides scope item content and documentation for project teams to leverage and use ready-to-access content and assets easily and quickly with the ease of the tool navigation and the added benefits it provides.

Lastly, test execution occurs by performing integration, regression, and UAT testing activities. The testing team prepares a test environment with the required test data as defined previously in the Testing workstream.

After all criteria have been collected and defined, test execution can begin.

Typical testing processes for the realize phase are as follows:

  1. Software developers perform unit tests in the development systems. Depending on the type and scope of the test cycle, various functional tests are performed.

  2. Manual testers are provided with the tester handout document and receive details regarding their test package by email.

  3. Automated tests are scheduled or started directly.

  4. Every test that is executed is logged and documented with test notes, and a test status is set manually or automatically

  5. If the system responds in an unexpected way during manual testing, for example, if an error message appears, the tester records the incident in the corresponding ITSM system, attaching screenshots, log messages, and so on. Usually, this also must be done manually, even for automated tests.

  6. The incident is sent to the persons responsible for the analysis and categorization of defects, who then correct the defect in the development system.

  7. The correction is transported to the test system according to the existing arrangements and timelines, where it’s then retested.


 

 

Summary

The key topic areas of configuration fit-to-standard or fit-gap (depending on the solution), migration, extensibility, and testing across the solutions.

It’s important to recall that these and previous activities require added attention to ensure the planning and execution that was performed in previous phases was captured correctly to avoid any unforeseen setbacks during the project implementation

Then, configuration was performed to meet the business processes, data migration and extensibility were executed, and test cases and plans were tested to ensure that all the previous workstream activities are in alignment and passed successfully to meet the project standards with the solution capabilities.
1 Comment