How to upload Test Cases into Test Steps Designer
With Focused Build – Test Steps, designing and executing manual tests with SAP Solution Manager is simplified and accelerated. Many features like content-driven test case design, guided test execution or in-depth reporting capabilities enable a testing experience which was not possible before in SAP Solution Manager.
In one of my previous blog posts I gave an overview on the most important capabilities & features of Focused Build – Test Steps. In this article I want to focus on how to upload existing Test Cases into SAP Solution Manager using Test Steps Designer.
When introducing Focused Build – Test Steps at a customer we usually find ourselves in a situation where plenty of time was already invested in describing manual test cases with tools like MS Excel. And of course you do not want to lose this content and start from scratch just because you implement a new tool for manual testing.
No need to be afraid: you can upload your existing test cases into SAP Solution Manager via the Upload Wizard of Test Steps Designer!
You can find the upload function in the application Test Steps Designer in your Fiori Launchpad:
At the bottom on the left you will find the “Upload” button which will navigate you to the Upload Wizard:
Step 1: Define Options for Upload
In the first step you can define the following options for your upload:
|Set Header row in file||Here you set the number of the row that contains the column headings of your test case. The default value that also corresponds to the sample file is set to “1”.|
|Set last row in file (optional)||This is an optional parameter which can be used in case you want to restrict the upload to a certain row range within your file.|
|Upload into SolDoc / with Executables||
With this option you can upload a test case and directly assign it to Solution Documentation including steps referring to executables. In this case you need to maintain the Solution / Branch context to which the test case should be assigned and where the executables can be found. As a prerequisite the file needs to contain the respective columns & content (SolDoc Path Occ ID, Step Executable, Logical Component Group).
|Solution/Branch||Here you select the Solution / Branch context where the test case should be assigned to and in which the executables can be found.|
|Validate only||You can activate this option in case you want to validate your file content without creating the test case (version).|
Step 2: Select the file that you want to upload
In the second step you select the file you want to upload. Since the file needs to follow a certain structure, it is recommended to download the sample file (see right upper corner of the wizard). With that you can learn how the structure should look like.
Please note: the file needs to be either in XLSX format (recommended) or a CSV file with UTF-8 encoding.
Step 3: Enter columns of your file mapping to test case attributes
In the third step you map the columns in your file to the test case / step attributes. Only mapped attributes will be considered during the upload. The wizard provides the column names based on the header row number you defined in step 1.
|Test Case Attribute||Description and Prerequisites for Upload|
|Test Case Name||This attribute is mandatory and defines the name of the test case. If you enter a name of an already existing test case, the upload wizard will create a new version of the test case.|
|Folder||Here you can define the folder to which the test case should be added. Folders are structure elements in Test Steps Designer that help to organize your test cases. You need to maintain the available folders in customizing before (see customizing of FB Test Steps in transaction SPRO). In the file you need to maintain the ID of the folder, not the label.|
|Test Case Version Title||Here you can maintain the title of the version that will be created automatically when the test case is uploaded.|
|Test Case Status Schema||Referring to the status customizing (see view cluster SMDDOCSTATUS in transaction SM34) you can maintain the status schema which shall be applied to the test case.|
|Test Case Status||Referring to the selected status schema (see above) and the customizing (see view cluster SMDDOCSTATUS in transaction SM34) you can maintain the initial status value of the test case. You need to maintain the ID, not the label of the status within the file.|
|Test Case Priority||Referring to the priority customizing (see maintenance view V_SMDDOCPRIORITY in transaction SM30) you can maintain an initial priority value here which will be set when the test case is created. You need to maintain the ID, not the label of the priority within the file.|
|Test Case Owner||Here you can define the owner of the test case either via Business Partner ID or User ID.|
|Test Case Notes||Here you can maintain working notes for this test case. They will be displayed in the tab “Notes” within Test Steps Designer.|
|Test Case Duration (min)||This is the duration (in minutes) of the test case that describes how long it takes to execute it by a tester.|
|Strict Step Sequence||This setting defines how testers can execute the test case: either in strict sequence (step by step) or flexibly choosing their own sequence. Potential values are “X” (strict) or blank (not strict).|
|Testing Mode||Here you can define whether different testers will share their results when executing the same test case. Alternatively, each tester will have an own execution with individual results. See this blog article for further details. Potential values are 1 (shared results) or 2 (individual results).|
|SolDoc Path Occ ID||If you want to add the test case directly to a node in Solution Documentation, you can maintain the Occurrence ID here. Please see the section below for further details how to find the right Occurrence ID.|
|Language||Test Steps test cases can contain multilingual texts. In this column of your file you need to specify the language of the referring content by entering a two-digit language code (e.g., EN, DE, FR).|
|Test Case Description||Here you can maintain a (multilingual) long text description for the test case.|
|Test Case Prerequisites||Here you can maintain a (multilingual) long text for prerequisites for the test case.|
|Test Case Exit Criteria||Here you can maintain a (multilingual) long text for exit criteria for the test case.|
|Step Number||This is the number of the step in sequence (1,2,3,…). Only number values are allowed here. Sub Steps can be maintained with a dot in between (e.g., 1.1, 1.2, 1.3)|
|Step Description||Here you can maintain the (translatable) long text description of the step|
|Step Expected Result||Here you can maintain the (translatable) long text expected results of the step|
|Step Test Instruction||Here you can maintain the (translatable) long text instructions of the step|
|Step Evidence||This defines whether the tester needs to add an evidence (e.g., a screenshot that proves a successful test execution). Potential values in your file are “X” (evidence required) or blank (evidence not required).|
|Step Executable||Here you can maintain an executable (e.g., transaction code, fiori app, etc.) that should be linked to the step. As prerequisite the executable needs to be maintained in the Solution Library within Solution Documentation. Furthermore, you need to maintain another column in your file with the ID of the Logical Component Group (LCG).|
|Logical Component Group||Here you need to maintain the ID of the LCG where the referring executable is located (see attribute Step Executable above).|
|Step Business Partner||Here you can define the partner of the step either via Business Partner ID or User ID. Please note: this is usually not a single person since testers will be assigned later via the Test Package. You should rather use this attribute for groups / organizational units to describe the group of persons that is meant to execute this step.|
|Hidden||With this flag you can mark a step as hidden for execution. Potential values are “X” (hidden) or blank (not hidden).|
|Custom Columns||If you use any custom column in your Test Steps setup, you will find them also in the sample file as well as the upload wizard. You can map each active custom column to a column within your file just like any other standard column mentioned above. Please note that for custom columns based on defined value sets (e.g., value help or dropdown columns) the given values in the file need to be IDs instead of labels.|
4. Start Upload
Finally, you press the button Start Upload to perform the upload according to your settings and column mappings. You will get a status message after the upload is done and you can find your test case afterwards in Test Steps Designer.
Please note: When uploading a Test Case with the same Name of an existing Test Case, a new Version of this Test Case will be created.
Uploading a Test Case directly into Solution Documentation
You can upload a Test Case directly into Solution Documentation via the attribute attribute “SolDoc Path Occ ID”. In the file you just maintain the Occurrence ID of the node where you want to upload the test case. But how do you get the Occurrence ID?
- Navigate to Solution Documentation (transaction SolDoc)
- Select the Solution/Branch/Node where you want to add your test case
- Switch to “List” view and make sure to filter only those nodes which are relevant for your test case upload
- Download the list as file to get all relevant Occurrence IDs in column “Path (OCC_ID)”
- Take over the Occurrence IDs into your upload file for Test Steps Designer
Please note: For the download function in Solution Documentation you need export authorizations via auth. object SM_SDOCADM.
Alternatively, you can also activate the display of the technical IDs for each node or element in Solution Documentation. This setting can be (de-)activated individually for your user via report RSMUD_GA_ENABLE_NODE_INFO_ATTR. Afterwards you will find the section Node Information in the properties pane in Solution Documentation. It contains the OCC_ID for the selected element.
Downloading a Test Case
You might also want to work on a new test case version of an already existing test case outside of Test Steps Designer. Therefore you can simply download the current version into an XLSX file and upload the edited (new) version later again via the upload wizard. The download function can be found at the bottom right of a selected test case. The downloaded file will contain all downloadable content in the right format which can be directly used for uploading it later.
Please note: a downloaded test case does not contain attachments or result attributes if any. Thus, you will not take over this data into a new version of the test case when uploading it with the wizard.
With Test Steps Designer the migration of manual test cases into the Test Steps type can be done easily. The upload functionality offers most of the test case attributes and plenty of options that help you migrating test cases into SAP Solution Manager.
For further reading you might be interested in this blog on how to migrate your test cases from Micro Focus ALM (HP QC / HP ALM) to Focused Build Test Steps.
7 Dec 2021: reworked whole blog post to cover the latest enhancements and updated screenshots.
7 Sep 2021: updated the section “New capabilities…” with latest enhancements of the Upload Functionality.
11 Sep 2020: added hint regarding auth. object SM_SDOCADM for download from SolDoc.