Every project is different and has its own unique objectives, scope, and priorities. Pivotal Systems Solutions' project team knows what to do in each project type. The SAP Project Types can be:
1. Implementation Project: We use the SAP Solution Manager to evaluate and implement our clients business process in SAP landscape.
2. Template Project: A template makes the project structure, or parts of it, with its assigned objects (documentation, test cases, IMG activities), available to other projects. These templates can be locked, completely or partially, against changes when they are used in other projects. To use templates in other systems, we transport them. Lets take an example to understand the logic of using templates. Say we have a SAP project which we would be delivering in two releases. In the 1st release we can create it as a template project and in the 2nd release we can have it as Implementation Project and thus make use of the documentation, test cases, IMG activities from the 1st project.
3. Upgrade Project: In this type of project, we upgrade existing systems.
4. Optimization Project: In this type of project, we optimize the flow of business processes, or the use of a software solution.
5. Safeguarding Project: In this type of project, we resolve a critical situation in the implementation or use of a SAP solution.
6. Maintenance Project: In this type of project, we provide maintenance services for a solution already implemented.
Test management can be broken into different phases: organization, planning, authoring, execution, and reporting. These are described in more detail below:
1. Test artefact and resource organization:
This requires organizing and maintaining an inventory of items to test, along with the various things used to perform the testing. This addresses how teams track dependencies and relationships among test assets. The most common types of test assets that need to be managed are:
2. Test planning: This phase addresses the questions of why, what, where, and when to test. The reason why a given test is created is called a test motivator (for example, a specific requirement must be validated). What should be tested is broken down into many test cases for a project. Where to test is answered by determining and documenting the needed software and hardware configurations. When to test is resolved by tracking iterations (or cycles, or time period) to the testing.
3. Test authoring: This phase is a process of capturing the specific steps required to complete a given test. This addresses the question of how something will be tested. This is where somewhat abstract test cases are developed into more detailed test steps, which in turn will become test scripts (either manual or automated).
4. Test execution: This phase entails running the tests by assembling sequences of test scripts into a suite of tests. This is a continuation of answering the question of how something will be tested (more specifically, how the testing will be conducted).
5. Test reporting: This last phase is how the various results of the testing effort are analyzed and communicated. This is used to determine the current status of project testing, as well as the overall level of quality of the application or system. The testing effort will produce a great deal of information. From this information, metrics can be extracted that define, measure, and track quality goals for the project. These quality metrics then need to be passed to whatever communication mechanism is used for the rest of the project metrics. A very common type of data produced by testing, one which is often a source for quality metrics, is defects. Defects are not static, but change over time. In addition, multiple defects are often related to one another. Effective defect tracking is crucial to both testing and development teams.
One way to sum up the objectives of test management is answering the following questions:
While this may seem straightforward enough at a high level, there are many obstacles that frequently arise in typical software development. These challenges are described below.