> Markdown version of [/videos/100215-smart-test-automation-the-experience-of-legacy-transformation?t=1093](https://www.wearedevelopers.com/videos/100215-smart-test-automation-the-experience-of-legacy-transformation?t=1093). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# SMART Test Automation - the experience of legacy transformation

Can too many unit tests derail a legacy migration? Discover how one engineering team abandoned the traditional test pyramid to safely modernize 3 million lines of banking code.

- **Speakers:** [Leszek Włodarski](https://www.wearedevelopers.com/@leszek-wlodarski)
- **Event:** World Congress 2026 Europe
- **Published:** July 10, 2026
- **Duration:** 30:42
- **URL:** https://www.wearedevelopers.com/videos/100215-smart-test-automation-the-experience-of-legacy-transformation

## Summary

Modernizing a 20-year-old core banking system requires navigating enormous technical debt without halting ongoing business operations. Relying on 3 million lines of JBasic code, a terminal interface, and zero test automation, mBank faced the threat of catastrophic "butterfly effects" during their migration to a .NET environment. The foundational strategy relied on an exact identity rule—ensuring the modernized system behaved identically to the legacy one, even mimicking its original flaws initially to guarantee safe, highly-controlled transformation.

Rather than adhering strictly to the traditional test pyramid, the engineering team realized that an overabundance of unit tests can act as "concrete" that locks in outdated architectures. Instead, they built a bespoke tool called "Squeezer" to extract manual testing flows and translate them into a massive suite of expressive middle-layer (integration and component) automated tests. By isolating execution in virtualized "bubbles" and mandating a strict "Keep it green. Red is red" standard, they successfully ran over 8,000 daily tests encompassing 80,000 steps across isolated test, release, and hotfix environments. This shift-left strategy allowed developers to spot and resolve regressions instantly without breaking shared environments.

Ultimately, upgrading the developer experience (DevEx) catalyzed the entire modernization. Transitioning from Notepad++ and terminal screens to C# APIs backed by Kubernetes and Postgres allowed the company to abandon IT "necromancy" and organically recruit modern talent to tackle a heritage system. Visualizing their non-traditional test architecture as a "spinning top," the lesson remains that large-scale integration tests must be constantly run and maintained to sustain momentum and prevent the system from toppling over.

**Keywords:** test automation, legacy system modernization, core banking transformation, developer experience, jbasic to .net migration, test pyramid, integration testing, middle-layer testing, automated regression testing, continuous testing, shift-left testing, exact behavioral parity, technical debt, software heritage, test data management, kubernetes, postgres, virtualized test environments

## Chapters

1. **Challenges of managing massive legacy core banking software** (00:05) — The reality of managing decades-old infrastructure alongside shiny new customer-facing applications requires dedicated transformation strategies.
1. **Defining the harsh reality of outdated legacy systems** (02:10) — Aging hardware and obsolete language support force modern engineers to work within severely limited environments.
1. **Managing architecture layers and the legacy butterfly effect** (04:06) — Hidden beneath shiny consumer interfaces, deeply nested legacy architectural layers are easily destabilized by seemingly minor changes elsewhere.
1. **Strategies for modernizing and mitigating legacy system risks** (06:36) — Why discarding outdated architecture often fails, and how continuous structural modernization permits an organized transition sequence.
1. **Rethinking the standard test pyramid for legacy software** (08:20) — Placing varying code components strategically across the unit, integration, and end-to-end layers ensures appropriate and comprehensive automated checks.
1. **Converting implicit manual knowledge into structured test automation** (10:55) — Building a specialized internal application to capture unstructured organizational logic facilitates a major leap in scheduled workflow executions.
1. **Establishing core principles for successful test automation adoption** (14:10) — Committing to virtualized execution environments and absolute pass states validates software quality assurance prior to production implementation.
1. **Migrating legacy source code to testable modern frameworks** (18:13) — Automating the direct translation of three million lines of code enables thorough verification through a distinctly more modern platform.
1. **Core architectural assumptions for expressive and scalable testing** (20:26) — Designing expressive test patterns within abstracted, fully mocked runtime environments keeps feedback loops immediate during complex pull requests.
1. **Accelerating developer productivity by introducing modern platform tooling** (22:13) — Upgrading environments to standardized tooling seamlessly replaces outdated platforms and significantly improves underlying engineering momentum.
1. **Reimagining test automation dynamics as spinning top mechanisms** (26:20) — Treating tests as active elements that demand continuous execution and maintenance prevents system failure instead of relying on a static coverage pyramid.

## Related Moments

- [Navigating legacy systems and unconventional software testing practices](https://www.wearedevelopers.com/videos/557-iot-the-road-to-sustainability) (from "IoT: The road to sustainability")
- [Challenges of applying test automation to legacy code](https://www.wearedevelopers.com/videos/309-how-to-tdd-in-legacy-code) (from "How to TDD in legacy code")
- [Real-world impact of modernizing automated internal operational tools](https://www.wearedevelopers.com/videos/100290-how-to-govern-vibe-coding-for-the-enterprise) (from "How to govern Vibe Coding for the Enterprise")
- [Shifting development challenges towards complex testing and team collaboration](https://www.wearedevelopers.com/videos/1459-the-evolving-landscape-of-application-development-insights-from-three-years-of-research) (from "The Evolving Landscape of Application Development: Insights from Three Years of Research")
- [Uncovering the technical root causes of low developer adoption](https://www.wearedevelopers.com/videos/100233-when-human-meets-canary) (from "When human meets canary")
- [Using test automation as a catalyst for team collaboration](https://www.wearedevelopers.com/videos/1668-how-to-add-test-automation-to-your-project-the-good-the-bad-and-the-ugly) (from "How to add test automation to your project: The good, the bad, and the ugly")

## Related Articles

- [Now is the time for industrialized software development](https://www.wearedevelopers.com/magazine/601-now-is-the-time-for-industrialized-software-development)
- [MLops – Deploying, Maintaining And Evolving Machine Learning Models in Production](https://www.wearedevelopers.com/magazine/115-mlops-deploying-maintaining-and-evolving-machine-learning-models-in-production)
- [Get Old, go Slow, Write Code!](https://www.wearedevelopers.com/magazine/81-get-old-go-slow-write-code)
- [Navigating the AI Shift](https://www.wearedevelopers.com/magazine/629-navigating-the-ai-shift)

## Related Jobs

- [Tribe Lead - ( Software) Engineering Centre of Excllence](https://www.wearedevelopers.com/jobs/ext/1475530-tribe-lead-software-engineering-centre-of-excllence) at **SD Worx**
- [Software Tester (f/m/d)](https://www.wearedevelopers.com/jobs/44712-software-tester-f-m-d) at **Power Plus Communications**
- [Engineer, Offensive Security Organization](https://www.wearedevelopers.com/jobs/ext/1992296-engineer-offensive-security-organization) at **Twilio**
- [QA Automation Engineer](https://www.wearedevelopers.com/jobs/ext/1414297-qa-automation-engineer) at **Bitpanda**
- [Penetration Tester / Red team Specialist](https://www.wearedevelopers.com/jobs/ext/293774-penetration-tester-red-team-specialist) at **Raiffeisen Bank International AG**
- [Staff, Analytics Engineer](https://www.wearedevelopers.com/jobs/ext/569504-staff-analytics-engineer) at **Twilio**