Yes, there is guidance on how to test extensions that is built with Custom Logic. However, I would separate this into two points:
Custom Logic Tracing is not the extension itself. It is mainly a troubleshooting and validation tool used to trace whether a BAdI implementation or custom logic is called, in which sequence it is called, and what parameter values are passed.
Testing should still be done as business process testing, not only technical tracing. For end to end validation, the Test Automation Tool and the Test Your Process app to create, run, and evaluate automated business process tests.
So, I recommend you:
Use Custom Logic to implement the BAdI or business object logic.
Use Custom Logic Tracing to technically confirm that the logic is triggered and the right parameters are passed.
Use manual business process testing or Test Your Processto confirm that the final business outcome is correct.
Make sure you retest the extension after upgrades, transports, or changes to the BAdI interface.
What this means in simple terms, is:
Custom Logic Tracing tells you whether the custom logic was called and with which values.
It does not replace functional, regression, integration, or UAT testing.
The real test should be based on the full business process where the extension is used.
If the extension affects posting, pricing, output, workflow, approval, or master data, the complete process should be tested from input to final document.
Bluesky
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.