Sign up to save your podcasts
Or
Share Why COBOL Developers Prefer Writing Tests in Java - Szymon Wałachowski, Bartosz Filipek
Share to email
Share to Facebook
Share to X
Share to email
Share to Facebook
Share to X
Or
Why COBOL Developers Prefer Writing Tests in Java - Szymon Wałachowski, Bartosz Filipek
When no IBM tool fits, two engineers built their own testing layer
📘 Free e-book: The 7 success factors of software testing. 25 years of project experience in one 33-page workbook, now also in English 👉 Get it for free
"The ultimate goal is to make people's life easier." - Bartosz Filipek
What happens when 40 years of custom decisions stack so high that even the standard testing tools from your own vendor stop working? With Bartosz Filipek and Szymon Wałachowski I talk about exactly that situation: a mainframe environment so deep in its own customization that the only way forward was to build one final bridge to the outside world. We dig into how they created a Java-based unit testing tool for COBOL developers, and what surprised me most is that COBOL programmers find it easier to write assertions in Java than in their own first language. We also get into code coverage, integration with tools like SonarQube and X-ray, and the long road of getting something as basic as a service account approved.
Szymon Wałachowski(https://www.linkedin.com/in/walachowski/) is a Senior Software Engineer, Professional Nerd, and part-time QA team member (the plot twist nobody saw coming).
He has broken things in JavaScript, Blockchain, ML, JVM, and Mainframes — which taught him to love QA so much that he now builds testing tools to help with modernization.
He enjoys modernizing legacy systems than build from scratch — because making ancient code dance with modern APIs while everyone says „that’s impossible” is his idea of fun.
Bartosz Filipek is an IT Architect with over 10 years of experience in software development, specializing in Java, Scala, and TypeScript. Passionate about automation and fostering strong collaboration between development teams and customers, he places a strong emphasis on quality assurance and testing.
In recent years, his focus has shifted toward architectural design and guiding teams toward future-ready solutions, while leveraging his extensive background in backend, frontend, and DevOps.
Highlights:
More Links with Insights:
View all episodes
By Richard Seidl | Software Development & Testing ExpertWhen no IBM tool fits, two engineers built their own testing layer
📘 Free e-book: The 7 success factors of software testing. 25 years of project experience in one 33-page workbook, now also in English 👉 Get it for free
"The ultimate goal is to make people's life easier." - Bartosz Filipek
What happens when 40 years of custom decisions stack so high that even the standard testing tools from your own vendor stop working? With Bartosz Filipek and Szymon Wałachowski I talk about exactly that situation: a mainframe environment so deep in its own customization that the only way forward was to build one final bridge to the outside world. We dig into how they created a Java-based unit testing tool for COBOL developers, and what surprised me most is that COBOL programmers find it easier to write assertions in Java than in their own first language. We also get into code coverage, integration with tools like SonarQube and X-ray, and the long road of getting something as basic as a service account approved.
Szymon Wałachowski(https://www.linkedin.com/in/walachowski/) is a Senior Software Engineer, Professional Nerd, and part-time QA team member (the plot twist nobody saw coming).
He has broken things in JavaScript, Blockchain, ML, JVM, and Mainframes — which taught him to love QA so much that he now builds testing tools to help with modernization.
He enjoys modernizing legacy systems than build from scratch — because making ancient code dance with modern APIs while everyone says „that’s impossible” is his idea of fun.
Bartosz Filipek is an IT Architect with over 10 years of experience in software development, specializing in Java, Scala, and TypeScript. Passionate about automation and fostering strong collaboration between development teams and customers, he places a strong emphasis on quality assurance and testing.
In recent years, his focus has shifted toward architectural design and guiding teams toward future-ready solutions, while leveraging his extensive background in backend, frontend, and DevOps.
Highlights:
More Links with Insights: