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.
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.
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.
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
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.
Thank you, we will try this soon
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.
How to change the separator by default to Comma in Step 3?
this is not possible. But with Focused Build SP4 the separator is determined automatically, so no need to set it manually in the wizard anymore.
In SP02 any option available to add additional test case attribute column in Step 2
no, there are no options to add additional attributes.
What are all the latest SAP notes needs to apply for Test step designer configuration in SP02?
please have a look at the central note: 2624462 - Focused Build: Technical collective note for ST-OST 200 SP02
It is recommended to regularly implement the latest version of the central note.
Thanks for the documentation , i have a question , do you know if possible export a test plan management from a Solman and import that test plan management for another Solman?. without the focus build tool
If you know how please tell me something .
Thanks for you help
export/import of Test Plans is not supported. However, you can export/import content of Solution Documentation including test cases and then create a similar test plan in the other SolMan based on the copy of the Solution content.
We would like to use customer fields for test steps result attribtes (e. g. Sales Order ID), because not a single tester will execute test activities but a group of testers.
Is it possible to add these attribute fields in upload process of test cases into test steps designer?
Many thanks in advance for your answer!
thanks for your question! Not so far - but we are aware of this requirement and will consider it for future SP planning...
We are implementing S/4HANA with Model Company (MC4MNC). SSM 7.2 SPS 09, FB 04.
The BIG question we have is how to get the test scripts that came with MC4MNC into FB Test Designer?
They are all in Word templates.
Look forward to any guidance.
we are already aware of this requirement and will consider it for future SP planning of Focused Build. In case you require urgent help in this regard and cannot wait for a future SP release, please feel free to contact me directly: SAP Consulting offers custom specific solutions in this case.
I wonder if there are any new updates to this question? I have the same need - a lot of testcases in MS word I like to import into FB. Manually cut and paste the testcases from word into excel for FB-import, is very time consuming and error-prone.
Help highly appreciated
Thanks in advance
thanks for getting back on this topic. Unfortunately, there is still no update. If you would like to emphasize the importance of your development request, I would recommend to raise it during the next Customer Influence Program for SAP Solution Manager/Focused Build.
However, my previous statement still holds: please feel free to contact me directly. Via SAP Consulting we can offer you a custom specific solution in this case.
Great post, thanks for it.
I tried it and it works quite fine.
But, I’m still having an issue.
I’ve populated the field “Test Case Notes” in the upload file and it appears in the created test case.
Though, when I’m creating a testplan-testpackage and select that particular test case, I can’t see this “Test Case Notes” anymore.
Any idea what went wrong?
Thanks in advance for your feedback.
thanks for your feedback, great to see that you could use the upload functionality successfully!
Regarding the notes field: Test Case Notes are only visible in "Test Steps Designer" during design time of the test case - not during execution time for the testers in "My Test Executions".
You can leave, for instance, working notes in this field which might be required for further processing, by a different colleague etc. You should not save any data in this field which is relevant during test execution.
I hope this helps.
I've created test cases, testplan, testpackage and assigned multiple testers to one testpackage.
One of the assigned testers added during the test execution an attachment into the results part of the testcase. See below picture. All of this is working fine. However, when one of the other assigned testers is willing to see these attachments, this tester doesn't see any attached documents. Any idea what is the reason for that? Missing authorisations? ...
Looking forward to receive your input.
Screenshot of testcase
in this case please open an Incident on component SV-SMG-OST-FB-TWB. The responsible colleagues will take a closer look then and give advice.
After maintaining the Test Result Attributes in the backend, Is there a way to upload which ones apply to a particular test case using .csv file against each of the test steps; or we will have to manually select the Test Result attributes using the Test Steps Designer application every time we upload a test case?
If there is an option to do so, which Attribute can be used in the .csv file to do this.
so far there is no option to cover result attributes during upload of test cases. You would have to manually maintain result attributes afterwards via Test Steps Designer.
We are already aware of this requirement and will consider it for future SP planning of Focused Build.
We are using Focused Build SP04 - and looks like there is no option to download the list of displayed nodes (to an excel file) which we plan to attach the test cases to - in order to get the attribute “SolDoc Path Occ ID” to use in the upload file. I also tried to do the same using the SAP demo system which is Focused Build SP06 version - and the option to download is also not there.
Can you please advise?
most likely this is due to missing authorizations. Please make sure that you have export authorizations via auth. object SM_SDOCADM.
Thanks Tobias! looks like it was indeed because I was missing the administrator role.
Hi Tobais Sir,
I am not able to see Focuses Build - Test Manger in the my Fiory launch pad..Could you please see below screen shot?. for that what role to be assigned to my User ID...please help me out...
Note: I need to create manual test cases in to SAP Solution Manager 7.2 and where do I crate manual test cases in solution manager please help me out sir....
with ST-OST the standard composite role SAP_OST_FB_TEST_M_COMP is shipped which would give you access to the tile group "Focused Build - Test Manager". With that role you can create Test Steps test cases.
Thank you so much sir , It really helped me a lot...
Upload the English CSV file but it is not converted to German (# in some character).
Is it require translation hub connectivity or how can i upload the German test case in test designer?
please make sure to provide CSV file with UTF-8 encoding otherwise special language dependent characters might not be transferred as expected. In MS Excel during "save as..." you should find the option CSV (UTF-8).
However, during upload so far you cannot provide multiple languages within a single file. That means you would always generate a new version in a particular language but not a single version with multiple languages. We are already aware of this issue and will provide an enhanced upload functionality in a future SP soon.
In general you can translate test steps test cases using translation hub into multiple languages. Please refer to my blog article on automated translation for further details.
I hope this helps.
Yes, we are using the CSV (UTF 8) file to upload in Test Designer.
Any other setting to save the file?
Also tried to download the example file in German but its shows only in English.
I am not sure if I get your problem.
The template file headings will always be in English.
In the first step of the wizard you can select the content language. This will then create a new version of your test case with texts in the defined language based on what you uploaded with the file.
In case you still perceive an issue I would suggest to open an incident at SAP Support Portal and enable a remote connection to your system. Please also describe in detail how to reproduce the error, best with some screenshots attached.
is there any possibility to enable an overlay? An overlay that indicates the test instructions step by step while executing the test in the test system? At the moment the testers need to switch between two windows of the test system and the solution manager system.
Thanks for your help!
thanks for this question. Currently this is not possible. But we are already aware of this need and will discuss it internally. However, I cannot make any statement if or when a corresponding function would be available.
thanks for your very quick answer!!! 🙂
Would be great to have it in the near future.
I have another question where I hope you can help.
We want to upgrade SolMan and Focused Build in the next weeks. We assume that there is SPS 12 with FB 07 planned to be available soon, but we can`t find any release notes nor fixed dates. Do you recommend to plan first the upgrade to SPS11 FB 06 or directly to upgrade to SPS 12 FB 07? We are already testing on Solution Manager with FB, so we want to make sure to have a reliable system.
Thanks for your suggestion!
for official information please refer to SAP Note 2806573 - Solution Manager SPS/FPS release schedule. You will be guided through SAP Support Portal and should find details on the planned release to customer.
thank you for your answer.
Thank you for the detailed article. Very helpful. We are able to effectively use Upload functionality.
I wanted to circle back on the same question that has been asked by multiple folks on this thread but since those responses are 1- 2 years old, I wanted to seek if there is any possibility (or enhancement) to map custom fields/columns to excel columns?
This is becoming a hindrance for various teams here as updating the custom fields manually after uploading test steps (especially test cases with over 40 - 50 steps (or over)) is not a good user experience.
thank you for your question & great to see that you can use the upload functionality.
Good news: since Focused Build SP07 you can also upload custom fields. The upload functionality was even further improved so that you can directly upload XLSX files without the need to save it as CSV UTF-8 anymore! Please note that the XLSX upload does not support color-formatting/background colors.
I hope this answers your question!
Thank you for your reply. This is good news, indeed.
We are currently on SP06. Is there any Note we can implement to use this feature with current SP or upgrading to SP07 is the only way around?
I am afraid there is no note available which would downport this functionality. In case you will upgrade, I would recommend to go for the latest SP (currently SP8).
Sure Tobias. Thank you for your assistance.
I've been finding hard to perform some reporting at Test Step level. We have some custom columns enabled and there is requirement from Projects to run some analytics to better understand the test steps progress.
I have explored Test Suite Dashboard - Execution Status but it would only display the results. There is no option to extract the data.
For example: If I want to understand the progress for all test steps with specific custom column lets say - WRICEF id, I can't find any possible way to extract that data.
Is there assistance you can provide us in this regard?
I get your point. For this requirement there is currently no standard report available and you would have to implement a custom report based on the database tables. If any further assistance is needed in this regard, we could offer our help within a consulting service. In that case please feel free to contact me directly.
Thank you for your response. Is it possible to share the Database tables and we will build a custom program based on Business needs?
the tables can be found in package /SALM/TM_TS_DESIGN. If you require further assistance please raise a consulting request via support portal.
Thanks for providing your insight into SAP Solution Manager 7.2. I have gone through your blogs and they are informative and it is well presented.
I have a question regarding Test Step Designer tile. We have installed SAP Solution Manager 7.2 with SP09 the thing is that I could not find the TSD tile. Is there any addon that I am missing.
What should by my approach to enable it.
Appreciate your help.
thanks for your positive feedback!
To activate Focused Build capabilities like Test Steps it is recommend to go through the instructions of the configuration guide. Here you find the guide for Focused Build SP04 which would be the right version corresponding to SP09 of Solution Manager.
Of course I would also recommend to upgrade to the latest SP of components ST and ST-OST in order to benefit from the enhanced functionalities. For Test Steps you will notice significant feature enhancements between ST-OST SP04 and SP08!
Thanks for your response. Appreciate it.
One last question. If we go ahead with Focused Build. Does Test Step Designer support upload of multiple(say 500) test cases from excel to SAP Solution Manager?
I have gone through the blog and questions but I could not get my head to understand if it supports multiple test cases upload in a single go.
yes, you can upload multiple test cases within a single file. For a better maintainability and error analysis (in case any) I would still suggest not to add 500 test cases at once but something between 10 - 50 depending on the number of steps and languages.
thanks for the helpful article. I have one question.
It is possible to import a Testcase with multiple languages in the same version with the upload from file function in the test steps designer? I can only import one language and then create another languages manually.
Thanks for your help.
Hi Tobias L.,
thanks for your question. Since Focused Build SP07 you can upload multiple languages in a single file: in column "Language" you simply add the language code (e.g., EN, DE, FR) and then maintain the different values for all languages in separate rows. Please see the sample file in the upload wizard for further details.
I hope this helps.
Hi Tobias M.,
Hello Tobias L.,
please see the sample upload file below. From your description above I understand that you added another row with the test case name + further header information. This content is not needed, you simply add all language specific content after the language column.
I hope this helps?
Hello...this article is great. One additional question a bit outside of this post. Do you know if you can create test cases from soldoc in mass generation based on process steps? I see I can create them from my structure one at a time, but wanted to generate a large number of them. Thanks.
thank you for your feedback on the article!
Currently there is no mass creation available based on process steps at different paths in Solution Documentation.
Of course one could implement a custom specific solution to achieve this. In case this is interesting for you, please reach out to me via personal message.
is It possible to copy the TEst Stepps from one solution to other solution via mass copy ?
the both solutions are in the same system
you can use Export/Import function of Solution Documentation / Solution Administration.
Details can be found, for instance, in SAP Help Portal.
I hope this helps?
The export and Import is none us but the issue is that the Test Steps do not have a description after importing and the source is the Original Solution.
We are not able to change the Test steps to the new solution
If you mean that this must work than I will create OSS . I am not sure if this is not working because software is designed so or there is a bug in system
please create an Incident in this case.
After I upload the test case file(which includes the tcode e.g. MM01 in the Test Step Executable column), I get the below message as seen in the screenshot, without the executable tcode added to the field like the other columns. As I understand, the only way to assign the test case to soldoc is to first upload the test case. How do I get the upload to include the executable as added in the file?
to upload a test case with executables, you need to activate the respective option ("Upload into SolDoc / with Executables") in the first step of the upload wizard and select the target solution.
Within the upload file you have to add the location in Solution Documentation where the test case should be placed. This is done via the column "SolDoc Path Occ ID". For further details on how to get the Occurrence ID, please have a look at the chapter above: "Uploading a Test Case directly into Solution Documentation".
Thanks Tobias. Very helpful blog.
Hi Tobias, after successfully uploading and testing the files in one of the test systems, I was trying to test the SAME file with the corrected OCC path id ,in the PROD env and got the following error. Are you familiar with this error?
this error happens in case the file contains a language, e.g. DE, which is not maintained in Test Steps General Settings on this system. Please review the maintained languages in customizing table /SALM/TM_C_GSET via transaction SM30 or via SPRO -> SAP Solution Manager -> Focused Build -> Test Suite Extensions -> Test Steps -> General Settings for Test Steps Application.
Thanks for the feedback!
With Focused Build SP11 you can upload a test case including Result Attributes, Solution Documentation Attributes as well as Header Attachments. However, the Header Attachments are based on what is already available in Test Steps Designer / Solution Manager Knowledge Warehouse and you can refer to these attachments via their technical IDs. It is not possible to upload new attachments via Excel.
Please see the sample file in the upload wizard for further details.