Lesson 2 of 5
Test cases from processes
9 min
Listen to this lesson
The recommended way to create a manual test case is from a solution process. Cloud ALM then knows which process the test covers, which scope it belongs to, and which activities it should contain. This lesson walks through the creation dialog and the choices that matter.
Creating the test case
- Open the Test Preparation app and filter by your project and scope.
- Choose Create and select the type Manual.
- Enter a title that says what the test proves, for example "Sell from stock, fleet customer, UAT".
- Confirm the project and select the scope.
- Select the solution process and, optionally, its solution process flow diagram.
- On the next step, choose which activities from the flow are in scope for this test case, and remove or add activities as needed.
- Save. The test case opens in status In Preparation.
- FilterTest Preparation filtered to the Contoso project and scope
- Create ManualTitle says what the test proves: "Sell from stock, fleet customer, UAT"
- Scope and processScope Contoso US, sell-from-stock solution process and its flow diagram
- Pick activitiesKeep order, delivery, goods issue and billing; drop what Contoso does not use
- SaveTest case opens In Preparation, ready for actions
Selecting a flow diagram is what makes the test case useful from the start: Cloud ALM prefills the activities from the process flow. For a sell-from-stock process those activities follow the steps of the flow, such as creating the sales order, delivering, posting goods issue and billing. You then refine them and add actions.
What comes from SAP Best Practices
SAP Best Practices content in SAP Signavio Process Navigator includes test scripts for each solution process, and Cloud ALM shows them as accelerators on the solution process. When you create a test case from a process, you get the structure. SAP's learning content for Private Edition notes that only the titles of the test procedures come across; the detailed actions are in the Best Practices test script, which you can use as the basis for your actions or upload as test case content.
| What you get from the process | What you still add |
|---|---|
| Link to scope, solution process and flow diagram | Actions with Contoso-specific instructions |
| Activities that follow the process flow | Expected results with real values (prices, accounts, quantities) |
| A starting point consistent with SAP Best Practices | Test data references: customers, products, plants |
| Placement in traceability and coverage reports | Evidence-required flags on the actions that matter |
Process-based creation gives structure; the team adds the specifics.
Contoso example
For order to cash, Priya's team creates "Sell from stock, fleet customer" in scope "Contoso US", from the sell-from-stock solution process. They keep the order, delivery, goods issue and billing activities, and drop an optional activity Contoso does not use. Under "Create sales order" they add actions: open the sales order app, enter sales area 1710 / 10 / 00, customer Great Lakes Fleet Services, product CMC-ALT-100, quantity 50, plant 1710; expected result: order saves with the agreed fleet price and a confirmed delivery date.
Volume: upload instead of typing
For dozens or hundreds of test cases, use Upload in Test Preparation with SAP's spreadsheet template. Each row is one action, and the activity title is repeated for each action under it. SAP's limits for one file are XLSX format, up to 5 MB, 500 test cases and 10,001 rows; SAP recommends no more than 20 activities and 100 actions per test case. You choose the scope at upload time, so prepare one file per scope, and do not add, rename or reorder columns.
- Load users firstEvery owner email in the file belongs to an existing Cloud ALM user
- Fill the templateOne row per action; repeat the activity title for each of its actions
- One file per scopeXLSX, up to 5 MB, 500 test cases and 10,001 rows; columns unchanged
- UploadChoose the scope at upload time in Test Preparation
- CheckSpot-check counts, owners and activities before review starts
Owners matter on upload. The template takes the test case owner as an email address; an address that does not yet belong to a Cloud ALM user is saved but shows as a former member until the person is added. Load users before content, or you will spend the first week of the cycle reassigning ownership by hand.
| Test case | Path it covers | What it proves |
|---|---|---|
| O2C sell from stock: standard | Fleet order for 50 x CMC-ALT-100 from plant 1710, delivered and billed | The normal process works end to end |
| O2C sell from stock: credit block | Order above Great Lakes Fleet Services' credit limit | The block is raised and only an authorized user can release it |
| O2C sell from stock: partial delivery | Only part of the quantity is in stock | Back-order and second delivery are handled correctly |
| O2C sell from stock: Chicago | Same order shipped from plant 1720 | Plant-specific settings and costs work |
What would you do?
A consultant created 40 Contoso test cases from processes but chose the wrong scope (Mexico instead of US) for all of them. The cycle starts in two weeks. What should Priya do first?
- Create manual test cases in Test Preparation from a scope, solution process and flow diagram.
- The flow diagram prefills activities; the team adds actions, expected results and data.
- Only the creation dialog title is editable after saving, so review assignments before you save.
- Use the spreadsheet upload for volume: one file per scope, within SAP's size and row limits.
Check your understanding · not graded
Lesson check
1. What does selecting a solution process flow diagram do when creating a test case?
2. In what status does a newly created test case start?
3. What is the maximum number of test cases in one upload file, per SAP's limits?
4. When uploading test cases, what is chosen once for the whole file?