Core banking replacement is not always a voluntary transformation. While some banks choose to modernize proactively, others are forced into core transformation due to vendor sunset timelines, unsupported legacy platforms, rising integration challenges, regulatory demands, shortage of skills to support legacy core, cybersecurity risks, or inability to support new digital products and customer expectations. Once that path is chosen, the journey brings significant complexity, dependencies, and unknowns. Testing becomes a critical success factor to reduce migration risk, validate business outcomes, and ensure a smooth transition. 

Here You’ll Learn About  

• Why every core modernization path requires strong testing discipline and enterprise alignment
• Common core testing challenges: scope gaps, fragmented journeys, and limited end-to-end validation
• Structured testing across configuration, migration, integration, regression, and non-functional areas
• Role of continuous testing, automation, and DevOps in improving release confidence
• Best practices for TCoE setup, environment strategy, test data management, and governance 

Deep Dive in Best Practices 

• Plan SME capacity early: Anticipate business SME shortages and train backups to avoid delays
• Design requirements rigorously: Ensure clarity, adaptability, and alignment across PSIT and UAT scenarios
• Anticipate dependency risks: Testing timelines can be impacted by requirement gaps and SME availability
• Manage shared environments proactively: Environment contention can create bottlenecks, so plan accordingly
• Align QA with business intent: Strong requirements and business context directly improve testing outcomes 

 Speakers in this Webinar: 

• Michael Harp, VP, Head of Testing for Core Transformation, Zions Bancorporation 

• John Kershner, Managing Director, Core 20/20 

• Amol Rukmangad, Head of Banking Delivery and Solutions, ValueMomentum