Skip to Content
Product Information

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!

Please note: this article mainly describes the upload functionality with Focused Build SP2. At the end you will find a section with details on new features that come with Focused Build SP3.

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: Select files you want to upload

In the first step you select files which you want to upload. Since these files need 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 CSV file needs to be stored in UTF-8 encoding.

 

Step 2: Enter columns of your file(s) mapping to test case attributes

In the second step you map the columns in your CSV file to the test case / step attributes. Only mapped attributes will be considered during the upload.

 

 

Test Case Attribute Description and Prerequisites for Upload
Test Case Name This attribute is mandatory and defines the name 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 CSV 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 initial version that will be created automatically when the test case is uploaded.
Test Case Status Referring to the status customizing (see view cluster SMDDOCSTATUS in transaction SM34) you can maintain an initial status value here which will be set when the test case is created. You need to maintain the ID, not (!) the label of the status within the CSV file. Please note: you cannot choose a released status here.
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 CSV 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 This is the duration of the test case that describes how long it takes to execute it by a tester.
Strict Step Sequence (FB SP3) 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 “empty” (not strict).
Testing Mode (FB SP3) 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 (FB SP3) If you want to add the test case directly to a node in Solution Documentation, you can maintain the Occurence ID here. Please see the section below for further details how to do this.
Test Case Description Here you can maintain a (translatable) long text description for the test case.
Test Case Prerequisites Here you can maintain a (translatable) long text for prerequisites for the test case.
Test Case Exit Criteria Here you can maintain a (translatable) 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.
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 CSV 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 CSV 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.

 

Step 3: Options for Upload

In the final step you define options for this upload. Afterwards you press the button “Start Upload” to trigger the upload as defined before.

Option Description
Set first row in file Here you set the number of the first row that contains the actual content of your test case. This must not be the header line that contains the column headings. In the sample file the correct value would be 2.
Set Header row in file (FB SP3) With FB SP3 the upload wizard supports an automatic column mapping based on the header line. In the sample file the correct value would be 1.
Set last row in file This is an optional parameter which can be used in case you want to restrict the upload to a certain row range within your CSV file.
Separator in CSV files Here you define which separator you use in your CSV file. This depends on your operating system / excel / file settings and can be either comma or semicolon.
Content Language Since the content of Test Steps test cases can be maintained in different languages you need to specify a content language for your upload. All long texts (e.g., description, prerequisites, expected results, etc.) will be maintained in that language when the test case is created.
Upload (into SolDoc) with Executables

If you want to upload a test case including steps that are mapped to executables, you need to activate this option. Afterwards you need to maintain the Solution / Branch context in which the executables are maintained. As a prerequisite you need to map the respective columns to the attributes Step Executable and Logical Component Group (see above).

With FB SP3 this option is also required in case you want to upload the test case directly into a node in Solution Documentation.

Solution/Branch Here you select the Solution / Branch context in which the executables are maintained.
Validate only You can activate this option in case you want to validate your file content without creating a test case.

And that’s it! You will get a status message after the upload is done that tells you about success or failure. If everything went well you will find your test case(s) immediately in Test Steps Designer by navigating to “All Test Cases” or the respective folder to which you uploaded them.

 

New Capabilities with Focused Build SP3

With FB SP3 the upload functionality has been further enhanced:

  • Direct Upload into Solution Documentation (details see below)
  • Further attributes (Strict Step Sequence, Testing Mode)
  • Completed Sample File (including all columns and samples for potential values)
  • Automated column mapping based on header line in file
  • Enhanced content checks to prevent failures during upload

 

Uploading a Test Case directly into Solution Documentation

With FB SP3 you can now upload Test Cases directly into SolDoc via the attribute attribute “SolDoc Path Occ ID”. In the CSV file you just maintain the Occurence ID of the node where you want to upload the test case. But how do you get this ID?

  1. Navigate to Solution Documentation (transaction SolDoc)
  2. Select the Solution/Branch/Node where you want to add your test case
  3. Switch to “List” view and make sure to filter only those nodes which are relevant for your test case upload
  4. Download the list as file to get all relevant Occurence IDs in column “Path (OCC_ID)”
  5. Take over the Occurence IDs into your upload file for Test Steps Designer

Conclusion

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. If this is even not enough for your individual migration path you still can apply the Test Steps API (see class /SALM/CL_TM_TS_TD_API) within a custom report to create test cases based on whatever format.

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.

8 Comments
You must be Logged on to comment or reply to a post.
  •  

    Hello Tobias,

     

    thank you for this article!

     

    Do you know if it’s possible to upload content for added columns in customizing ?

     

    The new columns don’t appear in step 2: Test case attribute mapping.

     

    Regards,

     

    Pascal

    • Hi Pascal,

      in Focused Build SP1 and SP2 it is not possible to add custom columns / attributes. Both applications, Test Steps Designer and My Test Execution, do not support additional columns – even though you can add columns in customizing there is no backend implementation that would handle those columns.

      Best regards

      Tobias

  • Hi

    We have intensively used Test Suit Focused Build Test Designer and found one very important missing point – this is extremely difficult to relate Test Cases to Business Processes during the upload of thousands Test Cases.

    This should be a connection field similar to the “Element” field in the Work Package, which will point the Test Case to the relevant Business Process in the Solution Documentation or at least the Test Case Title will pick up the Process Name as an attribute.

    Also the Defect Management should assign Defects at the Test Case step level and not at the Test Case Header level.

    We will be more than happy to discuss widely sour additional requirements off the Blog

    Cheers,

    Adi

     

    • Hi Adi,

      thanks for your feedback. With Focused Build SP3 (released today) we enhanced the upload capabilities. You can now add the property “SolDoc Path Occ ID” to your CSV file and then upload the test case directly into Solution Documentation. In this field you need to maintain the “Occurence ID” of the path in SolDoc. I will update this blog article with further details and describe how to do this.

      Regarding defect assignment at step level: we are aware of this requirement and will try to include it in the future roadmap of Test Steps.

      Cheers
      Tobias

  • Is there a way to create custom reports for test steps? The execution reports and Test suite analytics in general do not provide the same level of granularity as the MicroFocus ALM solution. In order for Solution Manager to be considered a viable complete solution for all Manual and Automated Testing the reports/analytics must be improved to include the ability to report on status at the step level as well as defects at the test step level.

    • Thanks for your question & feedback. In Focused Build Test Suite Dashboard you will find a detailed reporting on step level (see my other blog post on Test Steps). Currently an assignment of defects to a specific step within a test case is not possible. If you want to create custom reports you can also use the Test Steps API via class /SALM/CL_TM_TS_TE_API.

      • I agree you can get to step level status by drilling into each test scenario. If I have 50 test scenarios each containing 100+ steps I need to easily see and extract overall status as well as total number of steps passed, failed, incomplete…just as I can easily extract this from MicroFocus ALM. I do not want to drill into each and every scenario to see the step status. Similarly with CBTA automated tests, the execution report shows the status of each step but I do not want to view this report for all 50 scenarios. I need to report on overall steps completed. I think this is a gap in the Test Suite reporting/analytics area.