Testing SAP after MINOR CHANGES - how should you do it?
Learn more about the tool that helps you easily test SAP APIs after every change: https://int4.com/
Testing SAP after making big changes is crucial. And many SAP professionals are aware of that. But what about the minor changes? Is SAP Testing also a must? Watch the full conversation between the SAP testing experts - Michał Krawczyk & Michał Kowalczewski from Int4.
—
⚡ IMPORTANT LINKS ⚡
👉 YOUR NEXT STEP: Register for Official Free SAP Course "Avoid SAP S/4HANA Project Delays with Third-Party Systems Service Virtualization": https://int4.com/learning-sap-course-...
⭐ Book Int4 Suite Demo ⭐: https://int4.com/book-a-demo/
Get the copy of your book on SAP API Testing: https://www.sap-press.com/testing-sap...
—
Table of contents:
0:00 - Introduction
1:20 - What happens after a big SAP program finishes?
3:20 - What are the differences between BAU and Program/Project?
5:54 - Are business-as-usual only making minor changes?
7:00 - How can you define the size of change?
7:42 - You should TEST EVERYTHING after changes
10:30 - Are there local APIs that don't have dependencies?
12:18 - You can't deploy a "2 lines of code" change in 5 minutes
16:39 - Testing changes in BAU is HARD
19:07 - Deployment Windows have changed
21:30 - On-premise vs Cloud
26:00 - Can you use automated E2E testing?
27:36 - E2E testing downsides
30:08 - Int4 Suite testing capabilities
31:14 - Does it make sense to test all the minor changes?
33:30 - Summary
Website (Learn more about the solution): https://int4.com
LinkedIn (Bite-sized learning): / int4