Managing Manual and Automated Tests with SAP Cloud ALM

The main testing concepts in SAP Cloud ALM are:

• Lean
• Agile
• Flexible Test Levels
• Process -Oriented

With the Test Management capabilities in SAP Cloud ALM you can prepare and execute manual and automated tests. For some solutions like S/4HANA Cloud Public Edition, SAP Cloud ALM integrate S/4HANA Cloud Test Automation Tool that provides standard test cases which can be synchronized and executed with SAP Cloud ALM.

In addition, Tricentis Test Automation for SAP integrated with SAP Cloud ALM is a joint cloud-based offering from SAP and Tricentis. It combines the application lifecycle management capabilities of SAP Cloud ALM with the test automation capabilities of Tricentis, allowing you to design automated, functional, end-to-end software tests and manage them with test orchestration, execution monitoring, and reporting capabilities.

Details about SAP Cloud ALM Test Management:

• Easy to consume solution.
• Open to support all products in the future:
  • Cloud and On-Premise
  • SAP and non SAP​
• Test Orchestration:
  • Structure Test Cases via Scopes and Processes
  • Manual Functional Testing
  • Automated Functional Testing
  • Multiple Test Cycles via Test Plans
  • Traceability​

This figure demonstrates the acceleration of implementation and innovation through SAP Cloud ALM's advanced test management capabilities.

​Overview Page can be used as a central entry for all test related information and activities:

• Cards of interest and filters can be managed via views, for example to get a test centric view.
• All test entities and activities are managed with in the context of a project and scope.
• Option to use Tags for more granular view.

Creation of manual test cases is done based on business activities from the selected process flow.

Relevant business activities should be scoped so they are included in the test case.

The overall structure of the test case is created through the numerical order of these activities.

Use the Content tab to enhance each process activity with test actions:

• Title
• Instructions
• Expected Results

Additional tabs to assign:

• Requirements
• User Story

for traceability

Simple copy of test case to reuse existing test case content or just parts of it.

The General Information tab shows useful information like:

• Scope (inherited from Solution Process).
• Solution Process, Flow and Diagram.
• On top you can create and assign Tags to further categorize and classify your test cases.

When done, you can set the Test Case to Prepared and save, so it appears in the Test Execution Overview.

The figure shows the setting set test case to prepared.

Benefits:

• Supports multiple test cycles or roll-outs to multiple organizations re-using same or similar set of test cases.
• Test Plan Status to manage preparation, execution and completion of test phases or test cycles.
• Tester assignment per test case.
• Dedicated execution context (status and defects) per test plan.
• Start and end date can be set for test plan.
• Embedded draft handling to keep unsaved data.
• Efficient reporting and details per test plan.

This figure illustrates how lean testing operates effectively without traditional test plans.

This figure illustrates comprehensive testing procedures, both with and without test plans.

This figure demonstrates how easily test plans can be created and test cases assigned.

This figure demonstrates how effortlessly testers can be allocated to test cases during the creation of a test plan.

Benefits​:

• Navigation from Overview Page, Analytics and Traceability views.
• Search and various Filters can be used to find the relevant test cases.
• Allows users to set a Tester filter to view their own test cases or those of multiple users on a team.
• Test plans with status ‘In testing’ available for execution in your current test phase or test cycle.
• Test Case are grouped by Test Plans.
• Lean testing without the need to create test plans will be still available via filter value (None).
• Test Manager and Auditors can use this list view for reporting purpose.

Test Execution Detail view is used by tester to work on Test Actions:

• Read instructions, expected results and set status for each Test Action.
• Test run could be withdrawn when needed to rate current run as obsolete.

The figure shows the possible documentation of the test case results via comments including screenshots.

The figure illustrates, how defects are created.

Defect detail view:

• Description (rich text).
• Related Test Cases.
• References (for example, a URL to an app or documentation).
• Additional information with status, useful attributes, responsible team, role, assignee and tags for follow-up and reporting.

​In the test execution, you can download the test execution result to excel including most important data like:

• Who tested when.
• Number of total, passed, failed and untested actions.
• Number of defects.

The figure gives an overview of all available analytical tools.

​The Overview Page can be used as a central entry for all test-related information and activities:

• Cards of interest and filters can be managed via variants, for example, to have a test centric view.
• All test entities and activities are managed in the context of a project and scope.
• Option to use Tags and Test Plans for more granular view (hidden by default).

The figure shows various chart types.

​Monitor the progress of Test Execution with different chart types:

• Execution by Test Status, Filter by Test Plan.
• Burn-up of Executed Test Actions versus Burn-Down of Remaining Test Actions.

The Test Execution Analysis​ can be found as a tab in the Test Execution Analysis app.​

The report provides visibility on the number of actions remaining (work to be done for testers) before a test run can be finished​.

It offers a next level drilldown to see that a test run is in progress as the status alone is not enough. Progress can be viewed in terms of actions executed versus remaining​.

​The Manual test runs can be weighed by the number of actions to be done and comprises actions grouped into activities.

Monitor the progress of Defect Resolution with different chart types.

The figure shows the Check Readiness for Test Execution.

This figure illustrates how to identify which requirements are ready for test execution.

This figure illustrates how to identify which requirements are ready for deployment to production.

​Traceability apps now offer the next level of transparency by including Indirect Assignments.

​Indirect Assignments are indirectly related objects that are not assigned to the parent object, but contribute in the assessment of the overall readiness of the main object.​

Requirements Traceability: By switching on the test case in the indirect assignment button, test cases that are not assigned to the parent requirement but assigned to a child user story are also counted and included under the Test Execution and Test Preparation columns.

Requirements Traceability​: Defects are always indirectly related to requirements as the relationship exists only with test runs. ​When the Indirect Assignment – Defect is switched on, the defects column is shown in the matrix. ​The defects and its related test cases are shown in the pop-up.

User Story Traceability​: Defects are always indirectly related to user stories as the relationship exists only with test runs.​

When the Indirect Assignment – Defect is switched on, the defects column is shown in the matrix.

The defects and its related test cases are shown in the pop-up.

The figure gives basic information about test automation.

Watch the video to learn about the steps for preparing for automated test execution.

Watch the video to learn about the steps for executing the automated tests.