I see why some pick A since SAP likes to mention agile, but “current to future state” in B matches what OCM is really about, regardless of methodology. Focusing just on agile feels like a trap here. Anyone else think the phrasing in D is tempting but too narrow?
Why is everyone focusing on D? From what I've worked with, load and volume testing isn't directly available in SAP Cloud ALM test management. You can do manual and automated testing (B) and use test plans (C) right out of the box. Isn't D just possible if you bring external tools into play?
Wouldn't B and C be the showstoppers according to official SAP docs and typical practice test questions? Usually, if the execution pre-check fails or an execution variant isn't set up, PUT can't even start. Has anyone seen different guidance in the latest official guide?
Not sure if A and D would fully prevent SAP from running the PUT, I feel like B (failed execution pre-check) and C (missing execution variant) are system-level showstoppers. Sometimes 'data marked for deletion' just gets skipped, doesn't block the test. If someone has firsthand project experience, can they confirm that?