Because nobody can produce a list of what a transport changed, what those changes depend on, and what production actually uses. Without that list, testing everything is the only defensible option, so regression scope stays the same size every release regardless of what shipped.
Key Takeaways
- 01
SAP regression takes weeks because nobody can prove what a transport touched, so teams rationally test everything.
- 02
SAP's own guidance says 40 to 60% of custom ABAP code never executes in production, which inflates test scope with dead code.
- 03
Change impact analysis works in 3 steps. It resolves every object a transport touches including standard SAP code, weights the graph with production usage, and matches scope against existing tests.
- 04
Percentage of test cases executed measures team activity, not test coverage. The better metric is the share of changed and used objects validated before the release gate.
- 05
Fiori sits on OData services and CDS views that ABAP tooling cannot see, so a CDS change can silently break apps.
- 06
LiveCompare is sold standalone, as SAP Change Impact Analysis, or bundled with Tricentis Tosca as SAP Enterprise Continuous Testing, and buying the wrong packaging is a common avoidable mistake.
Why Your SAP Regression Takes 3 Weeks (And How to Prove It): transcript and chapter notes
Your SAP regression testing takes so long because nobody can prove what a transport actually touched. Not because of resource capacity or a narrow windows. This video shows you how to verify this in your own shop this week, without buying anything.
We cover how to ask your team for a list of what your last transport changed, its dependencies, and what production actually uses.
Chris Carpenter from Merito also discusses why testing everything is a rational response to missing information, SAP's own data showing 40 to 60% of custom ABAP code never executes in production, and how change impact analysis works in 3 steps compared to a basic where-used report.
The video also breaks down why "percentage of test cases executed" is not test coverage, the Fiori and S/4HANA layers your ABAP tooling can't see (OData, CDS views, compatibility views), and where LiveCompare fits whether you buy it standalone, as SAP Change Impact Analysis, or bundled with Tricentis Tosca as SAP Enterprise Continuous Testing.
Chris also maps the SAP Integrated Toolchain (LeanIX, Signavio, Syniti, Cloud ALM, Tosca, WalkMe) and shares 4 signals that your regression scope is set by habit instead of risk.
Read the full article: https://www.merito.com/resources/blogs/you-test-everything-because-nobody-can-prove-what-the-transport-touched
Book a consultation (or claim your free lunch if your team produces that list in under an hour): https://www.merito.com/book-consultation
Chris's team will help you scope the right LiveCompare, SAP CIA, or Tosca bundle for your landscape, and tell you honestly if you're not ready for one yet.
Frequently Asked Questions
Why Your SAP Regression Takes 3 Weeks (And How to Prove It): questions and answers
Consultation request
Book a consultation with Merito
Use this form to talk through the workflow, platform fit, and delivery priorities behind this video with a Merito specialist.
Discovery
Turn the video into a working plan
Use the conversation to translate what you saw here into a practical next step for your team.
Alignment
Get the right specialist involved
We route the request to the team best suited for platform strategy, implementation, quality, or AppSec delivery work.
Get Started
Secure intake workflow
The request is protected by reCAPTCHA Enterprise and processed through Merito's standard consultation flow.