Where errors emerge in SAP projects – and how to stop them

The integration of the Test Management (TM) stream into the SAP Activate project methodology is a key success factor for SAP projects. Within SAP Activate, all project activities are structured into clearly defined phases. Test management is embedded as its own stream within this methodology and contributes specific deliverables in each phase, with core test planning activities beginning toward the end of the Prepare phase and extending into the Realize phase.

Test management process: test planning

It establishes the foundation for effective test execution – even in the early stages of a project. The goal of testing is not to uncover as many defects as possible, but to ensure that systems and interfaces consistently and correctly execute the intended requirements.

To achieve this goal, test management at Natuvion follows the International Software Testing Qualifications Board standard (ISTQB). This creates a consistent foundation for high-quality test execution through standardized terminology and approaches, such as test case design. As a result, the testing process can be carried out efficiently and effectively—not only in the current project but also in future initiatives, such as system upgrades.

Since even relatively small systems lead to an exponential increase in possible inputs, paths, and instructions, complete test coverage is not feasible in practice. For this reason, careful planning of testing activities is essential to ensure the highest possible quality while minimizing the risk of defects.

Creating structure and ensuring quality

For the success and credibility of any testing initiative, it is essential to design, execute, and consistently follow a clearly defined test process. The quality of testing activities depends heavily on thorough and early test planning. While planning and control extend throughout the entire project lifecycle, starting no later than the Explore phase is critical in order to identify dependencies—not only within the project structure but also in business implementation—and to minimize risks at an early stage.

Test planning acivities

Test planning includes all activities required to define and manage the testing process. It forms the fundamental organizational and methodological framework for all subsequent testing activities.

The test strategy

This is developed as an overarching strategy that defines the general approach to testing, including the types of tests, test phases, and methods to be used. A test strategy may apply across programs as well as multiple projects.

Detailed test concept

Based on the test strategy, the Natuvion approach develops a detailed test concept that describes the organizational implementation. It includes, among other things, the tools used, documentation requirements, and the organization of test phases. A key element is defining the test scope, which is based on project goals, system requirements, and relevant business processes. To ensure a structured process, a detailed test schedule is created that takes into account milestones, test cycles, dependencies on other project phases and streams, as well as time buffers.

Communication model

In addition, there is a communication model that regulates the flow of information between the test team, business departments, development, and project management. This model defines communication channels, escalation paths, and reporting intervals to ensure transparency and responsiveness. At the same time, it assigns clear roles and responsibilities to all participants involved in testing, such as test managers, test analysts, testers, and defect managers.

Test execution

For test execution, the need for test data is determined, including the type of data as well as its source and preparation. Defining the required test environments—including hardware, software, network configuration, and interfaces—ensures that they are as close to production as possible. Finally, staffing requirements for test execution are determined to ensure that sufficient resources are available to complete the planned test scope within the defined timeframe.

Completion of test planning

Test planning concludes with the completion of the test concept, which is approved by project management. This document is not static but is continuously reviewed across phases and adapted to the specific conditions of the project.

Test management tools

A key component of test planning is the early selection and setup of a suitable test management tool. At this stage, it must be determined which system will be used to document test cases, monitor progress, and handle reporting. The choice of a specific tool significantly impacts the structure of test documentation as well as the efficiency of subsequent test execution. When selecting a tool, it is important to ensure that test methods and phases can be properly represented and that it can deliver structured, project-wide reporting. For example, test cases can be sequenced across different test plans to reflect dependencies, such as those in an end-to-end business process, or testers can be assigned to specific test cases to clearly define responsibilities. Integration of the tool into existing project and development systems is also prepared during the planning phase to ensure a consistent information base and test coverage for all stakeholders. The final decision on the selection of test tools lies with the customer, while Natuvion provides guidance in tool selection and helps establish the structures required for effective test management.

Test methods and phases

Another central component of test planning is defining the test methods and phases to be used in the project. These must be determined early, as they have a direct impact on the project and test schedule, resource allocation, and test scope. Based on project goals, functional scope, time constraints, and the chosen migration strategy, appropriate methods and phases are defined. Typical examples include:

• E2E testing
  

• Non-functional testing
  

• Automated testing
  

• Exploratory testing

The corresponding test phases may include component or module testing, integration testing, regression testing, user acceptance testing (UAT), and migration testing. A clear and documented definition during the planning phase ensures that test preparation can be carried out effectively, and that later adjustments are kept to a minimum.

Dependencies and framework conditions

The quality of test planning largely depends on the overall project plan. Without a coordinated project plan, companies will not be able to create realistic timelines or resource plans. A solid test concept requires clearly defined framework conditions—such as the migration approach, available test data, and documented business processes (e.g., in the form of a process map).

Test planning must be integrated, not isolated. Close coordination within the project and clearly defined responsibilities are essential. Test management does not only operate internally (e.g., coordination, testers) but must actively communicate with other project areas and gather all the necessary information.