A long-awaited test management functionality is now also available in SAP Solution Manager 7.2. With Focused Build, there is the function of the test steps designer. In this blogpost I would like to share my experience using the test steps designer. They are based on the release ST-OST 200 SP02.
Using the Test Steps Designer has several advantages.
- It is possible to set a status per test step. This allows more detailed test results at step level.
- The test cases can be created in multiple languages. The language can be easily changed per test case.
- Highly user-friendly, as consistent Fiori / UI5 appearance.
The use of the test steps designer
The application of the test steps designer from the creation of the test cases to the test execution is described below and the most important points are discussed.
Three ways for creation of test cases
Creation of a test case via the Fiori app “Test Steps Designer”.
Create the test case directly in the solution documentation with the re-use of your process structure.
Upload test cases via CSV file.
Description of the test steps
The test steps can be completed by using the fields “Description”, “Instructions”and “Expected Result”. In addition, an executable can be assigned to each test step. However, this requires a link between the test case and the solution documentation.
As described, there is great added value if the test case is created directly in the solution documentation, because the elements of the process structure and the executable are taken over into the test steps. The test case is therefore already linked to the solution documentation.
The test execution is kept very clear with the test step designer. As soon as the status is set per test step, a small window area appears on the right where the “actual result” can be stored. If required, further mandatory fields such as “test result attributes” can be specified.
Generally, however, the principle “less is more” applies here, because the more columns and fields are given to the testers, the more confusing the whole mask becomes. The testers should be able to work easily with the test steps designer and they need just a few clicks and inputs to record the status and the result.
Improvement potential for the test steps designer
Since the test steps designer is still relatively new, there are certain functionalities which are still missing in the current version. Summarized these are:
- The performance when calling and setting the test step status can be improved.
- Bulk processing for setting the test step status for several marked test steps or all test steps is currently missing.
- A WYSIWYG editor for the description of the test steps to format the test case description.
- Embedding images in the test case description for a detailed test statement.
- Creating parameters with value selections that can be used in the test case description.
- Detecting and Linking a Defect at level test step (currently only possible at the level of the entire test case).
- Excel Download function for the entire test case including all test steps and attributes.
- Save the mapping (columns from the CSV file) when uploading test cases.
- Assign masses of uploaded test cases to nodes in the solution documentation.
- Create a test case based on process variants and process diagrams.
- Use the same test case status values as for manual test cases with test documents.
- Show a column for comments and document numbers in the overview with which document numbers can be entered for each test step, for transfer to the following testers.
I am very confident that SAP has already recognized many of these points and will work on it.
With the Test Steps Designer, SAP has integrated a state-of-the-art functionality into the Solution Manager. Especially for long test chains like E2E processes, this brings great advantages. Even in the regulated environment, where detailed test results and evidence must be provided, the test steps designer is an ideal solution.
If the Teststep Designer continues to be enhanced with functionality in the future, the user-friendliness and simplicity of use will always be important. The testers must not be prevented from overseeing their actual task – testing – by overly large administrations.