Tell us what you think

We want to create the best possible experience for our learners. Your feedback helps us to improve the experience for everyone.

Planning and Executing Testing

Objective

After completing this lesson, you will be able to illustrate the creation and execution of test cases as well as the creation and processing of defects.

Testing: Plan and Execution

The figure illustrates the creation of a test case during test planning and an overview about tests execution activities.

Test management provides functionalities for testing in SAP Cloud ALM comprise test planning and test execution.

The figure illustrates a test case and the test execution overview screens.

Note

Test Case: Description or script to verify/validate requested/existing functionality.
Defect: Entity to address and resolve software defects found during testing.

Details of Test Management:

Supports lean, agile, and process-oriented testing.
Reuse solution process activities as test steps.
Create test plan.
Manual functional testing.
Integration of automated test tools.
Test execution inclusive history.
Test execution analytics including requirements traceability.

Further details:

Main functionalities of test management are listed above.
Reuse solution process activities as test steps: creation of test cases similar to test steps in SolMan, no document based test cases.
Starting point for creation of test cases is always a process.
Usage of Test Plans is optional.

Plan and Execute Testing - Test Plans

Example of different test plans in the system.

Test Plans are the key element in managing test activities. With test plans, for example for multiple test cycles or roll-outs, re-using same or similar set of test cases can be handled.

Supports multiple test cycles or roll-outs re-using same or similar set of test cases.

Available Test Plan status are:

To manage preparation.
Execution
Completion of test phases or test cycles.

Dedicated execution context (status and defects) per test plan.

Start and end date can be set.

Embedded draft handling.

Plan and Execute Testing - Test Automation Approach Orchestrated by SAP Cloud ALM

SAP Cloud ALM can integrate with two different tools for test automation. These are: SAP S/4HANA cloud Test Automation tool (TAT) and Tricentis Test Automation for Cloud ALM (TTA)

Plan and Execute Testing - Test Automation with SAP S/4HANA Cloud TAT

The figure illustrates the test automation with SAP S/4HANA Cloud TAT.

If TAT is the test automation tool of choice, the infrastructure for test automation comprises the three pillars: SAP Cloud ALM, TAT as well as the Systems under Test (SUT).

Test Automation With SAP Cloud ALM and Tricentis

If TTA is the test automation tool of choice, the infrastructure for test automation comprised the three pillars: SAP Cloud ALM, TTA as well as the customer landscape.

Another test automation option is: SAP S/4HANA Cloud Test Automation.

Benefits of test automation:

Time savings
Error reduction
Scalability
Repeatability
Efficient execution

In the integration, SAP Cloud ALM manages the entities for business processes, requirements, user stories, and defects. These are all linked to manual and automated test cases.

For automated test cases, the test automation endpoint connects to TTA via test automation APIs. SAP Cloud ALM mainly focuses on orchestration, but execution is also possible from this platform. Reporting and triggering of test cases are available in SAP Cloud ALM.

For each SAP Cloud ALM tenant, there is a corresponding Tricentis tenant. The automated test cases are managed by TTA, and only necessary information is synchronized using the transformation API’s. TTA is the target environment for the automation, including the creation, maintenance, customization, and execution of test cases.

In TTA, the test execution is facilitated by a piece of software called an automation agent.

The agent program can be installed on:

A local machine.
Virtual machine.
Even in a container.

These agents:

On-premises execution agents (only used in on-premises systems):
Hosted execution agents
- private (=local test, test results only visible to you) and
- shared
connect to TTA and are always ready to receive and execute tests.

Exercises in the Unit: Planning and Executing Testing

Flowchart of all steps of the exercises, the steps, which are processed in the next exercise, are highlighted.

The figure illustrates all steps, performed in the exercises of this training.

In this unit, there are three exercises in which you will do the following:

Create a Test Case

Create a new test case.
Add mandatory information and necessary additional information.
Add activities to the test case.
Specify and add test steps.
Mark the test case as prepared, and add tag to cluster test cases.

Execute the Test Case

Execute the test case, and set test steps to pass or fail.

Create a Defect

Create defect from test execution.
Add mandatory information and necessary additional information.

Create a Test Case

Business Scenario

As a Test Designer, you are asked to prepare the test steps for test cases to be tested during the next test phase.

Task Flow

In this exercise, you will perform the following steps:

Use the Test Preparation function.
Create a test case with process assignment.
Elaborate your test case including step description and expected results.

Exercise Information

Note

In this exercise, when the values include ## or XX, replace the character with a two-digit number (01–30).

Exercise Options

Perform the exercise by entering the requested values in the fields of the simulation below.

ExerciseStart Exercise

Note

All text input fields can be confirmed by choosing the Tab or Enter key or by leaving the text box.

How to Assign a User Story and Requirements

Business Scenario

As a Test Designer, you are asked to assign User Story and Requirement to a Test Cases to ensure full test coverage for the next test phase.

Task Flow

Follow these steps:

Open an existing Test Case.
Assign a User Story.
Assign a Requirement.

DemoStart Demo

Execute the Test Cases

Business Scenario

As a tester, you are asked to execute test cases prepared for the next test phase.

Task Flow

In this exercise, you will perform the following steps:

Use the Test Execution function.
Execute the test case for every single step.
For every test step, document the actual result, and note if it is passed or failed.
Provide additional comments or documents if required.

Exercise Information

Note

In this exercise, when the values include ## or XX, replace the character with a two-digit number (01–30).

Exercise Options

Perform the exercise by entering the requested values in the fields of the simulation below.

ExerciseStart Exercise

Note

All text input fields can be confirmed by choosing the Tab or Enter key or by leaving the text box.

Create a Defect

Business Scenario

As a tester, you want to create a defect for a test case that failed.

Task Flow

In this exercise, you will perform the following steps:

Create a defect for the test step that failed.
Add basic information, for example, title, description, priority.
Optional: Add additional attributes such as the desired completion date, the roles, or teams responsible for solving the defect.

Exercise Information

Note

In this exercise, when the values include ## or XX, replace the character with a two-digit number (01–30).

Exercise Options

Perform the exercise by entering the requested values in the fields of the simulation below.

ExerciseStart Exercise

Note

All text input fields can be confirmed by choosing the Tab or Enter key or by leaving the text box.

How to Correct a Defect

Business Scenario

As a member of a development team, you have to fix a test defect created during a test phase and inform a tester that a retest can be performed.

Task Flow

Follow these steps:

Open a test defect assigned to you or your team.
Analyze and if necessary, fix the issue.
Inform tester that a retest can be performed.

DemoStart Demo

Continue to quiz