Unassigned test cases in Cloud ALM test execution

[sebiemb]

Hello experts,

I am relatively new in the SAP world, more particularly in SAP Cloud ALM.

I am currently working in a migration project, from an ECC to S4H, and we are using the SAP Cloud ALM tool for test management. This implies: test case preparation, test plan preparation, test case executions and monitoring.

While the construction of test cases and plans has worked accordingly, I have been facing an issue that I'd like to find an answer to (in order to avoid these situations in the future) and that I will be complimenting with screenshots (from DEMO system) provided.

For some context,

1. Test preparation (Screenshot: 1. Test preparation)

I have created 3 test cases as shown, with status set to "Prepared".

2. Test plans (Screenshots: 1. Test plan & 2. Test plan)

I have also created 1 test plan to which I have assigned the 3 previously created test cases and, to each one of them a tester; test plan's status is set to "In testing".

3. Test execution (Screenshots: 1. Test execution, 2. Test execution & 3. Test execution)

When visualizing the aplication "Test execution" I observe: Instead of having a list consisting of 3 test cases pending for execution (those which have been assigned to the test plan), we have a list of 6. Out of these 6, 3 of them are shown with no test plan nor tester assigned to them (Highlighted as "None" or empty) meanwhile, on the contrary, the rest, show, indeed, a test plan and a tester assigned to them, which is what we want.

4. Overview (Screenshots: 1. Overview & 2. Overview)

When visualizing the overview app for testing, I have to set a filter in "Test plans" in order to rule out those test cases without assignment, so we can maintain an effective monitoring of test executions.

What can I do, or undo, experts, in order to avoid this situation in the future and so the quantity of test executions corresponds solely to those that have been assigned a test plan and a tester?

Thank in advance,

Sebastián

[RiccardoEscher · Accepted solution]

Hello Sebastián,

somehow it works as designed :-).

But the real reason is the evolution of the Cloud ALM Test Suite. At the beginning there were only stand-alone Test Cases. Every stand-alone Test Case offered only one eternal result instance. This means that when you execute the Test Case two times, the system will consider this a 4-eyes execution of the same Test Case and the reporting will always show only one overall status, having the status of this overall result (success, failure) the worst case combination of all executions. If you need a second run of the Test Case for a regression test later on, then you have to copy the Test Case, thus creating a new stand-alone Test Case as a clone of the old one.

This was a little bit ugly, people used external tools and some upload facility for additional test runs.

Therefore, SAP kindly introduced Test Plans. Now every Test Case can be assigned to 1 .. n Test Plans, and every Test Execution inside a Test Plan will be an own instance. This means that for every new test run you can copy the Test Plan, or create a new one, and the Test Case will offer new evaluations: during the run of TestPlan01 the Test Case was evaluated to Success, during a later run of TestPlan02 the same Test Case may evaluate to Failure. In the reporting you will see these differences.

Now to your problem: decisive is the "Test Plan Status" selection, with which you can choose between old stile (stand-alone Test Case) and new stile (Test Case inside a Test Plan). You problem might be that you wish to force the new stile. When you don't touch the "Standard" view, it selects only the new stile by filtering for Test Plans "in Testing".

But sure, testers can be difficult to steer, and according to Murphy's Law every mistake will find someone who will do it, so I can imagine some sort of governance functionality, which forces the desired Test Plan Status (or prohibits the selection of "(None)").

You may consider to create an improvement request here: https://influence.sap.com/sap/ino/#/campaign/3501

[paula_augedahl · Accepted solution]

Dear Sebastian, since an answer was provided to your question, and there has been no other activity on the topic, we have accepted the answer as a solution on your behalf. You can unaccept it anytime if the answer provided was not helpful enough or if you have further questions. Thank you for bringing this question to SAP Community! Best regards, Paula