Software Testing Unleashed - Better Teams. Better Software. Better World.

In this episode, I talk with Daniel Knott about the real pains in testing and what comes next. Why do managers cut quality when money gets tight. We look at AI and low code that spit out apps fast, often without clear architecture. We warn about skipping performance and security. We also reflect on how testers can sell value in business terms. Speak revenue, KPIs, and user happiness, not code coverage. Daniel says domain knowledge may beat deep coding as AI writes more code. We explore prompt reviews as a new shift left habit.

In this episode, I talk with Kat Obring about the tester as an influencer. We explore how to stop saying everything is broken and start speaking the language of stakeholders. Bring evidence, not opinions. Say "the Safari sign up button fails and 20 percent of users are blocked". We share a 15 second check before stand up, and pairing early so testing is part of development, not a mini waterfall at the end. Pick small battles and run one or two week experiments. If it works, keep it. If not, drop it. Influence without authority grows from trust and habits.

In this episode, I talk with Maciej Wyrodek about moving from Cypress to Playwright. We talked about why Cypress started to work against the team: opinionated style, plugin churn, iFrames, flaky screenshots, and a pricing wall around parallel runs. Maciej's answer was a hands on hackathon with devs and testers. Playwright won. The migration starts with their top 10 flows and production smoke checks.

In this episode, I talk with Gitte Ottosen about cross functional teams, quality engineering, and how deep skills fit in agile work. We question the Everyone owns quality mantra. If all own it, who does the hard parts. Gitte calls out mechanical agile and the comb shape myth that makes people wide and shallow. We talk about what Scrum expects from a team and why testers still bring sharp value. AI may take easy tasks, yet we need critical thinking and solid test design to judge its output.

In this episode, I talk to Maroš Kutschy, a QA technical lead passionate about automation testing and self-improvement. We go into the topic of nonviolent communication and its impact on tech teams. Maroš explains its four core components: observations, feelings, needs, and requests. We discuss how simple changes in language can greatly improve team dynamics and communication. For example, he illustrates how expressing yourself without blame opens up clearer dialogue.

In this episode, I talk with Dmitrij Nikolajev about teaching software testing to the next generation. Dmitrij, who balances roles at InSoft and Vilnius University, shares his approach to making software testing engaging for students. He focuses on practical, hands-on experience, using tools like Postman and Selenium to teach automation and performance testing. Dmitrij redesigned his course to appeal to both new learners and those already in the industry. He leverages real-world examples to highlight the importance of testing, encouraging students to understand the consequences of failures. We also talk about the role of AI tools like ChatGPT in the learning process and their impact on student progress.

In this episode, I chat with Mary Lynn Manns about the ever-tricky topic of change in tech. Mary Lynn is a consultant, pushing ideas forward despite resistance. We explore why good ideas alone often aren't enough and why change can falter when we rely solely on logic and ignore emotions. We discuss how to effectively engage skeptics and build emotional connections that go beyond simple presentations. Mary Lynn shares practical techniques for leading change from any role, aiming to minimize resistance and maximize impact.

In this episode, I chat with Derk-Jan de Grood. We explore what it means to live agility beyond just following frameworks. Derk-Jan shares insights on scaling skills over frameworks and connecting strategy to team actions. We discuss common pitfalls where quality often falls through the cracks, particularly at the management level. There's a focus on breaking down testing and improvement into small, actionable practices. It's all about making Agile effective and meaningful.

In this episode, I chat with Nikhil Barthwal about property-based testing. We go into how property-based testing can uncover the hidden bugs that often slip past human testers. With its capacity to automatically generate a multitude of test cases, this method helps us see beyond typical limitations. Nikhil also shares when property-based testing may not be ideal, like when it incurs high resource costs. He emphasizes that this approach serves as an assistant to testers rather than a replacement, enhancing productivity and reliability.

In this episode I talk with Eoin Woods about integrating security from the start of software development. Eoin, an expert in software architecture, explains why security often gets overlooked until the last minute. We explore why engineers find security daunting and discuss making it a standard part of development. Eoin shares design principles like defense in depth and cautions against custom security solutions.

In this episode I talk to Gien Verschatse and Kenny Baas-Schwegler about the challenges of collaborative software design, especially the disconnect between development teams and business stakeholders. Both Gien and Kenny shared stories of communication gaps, assumptions in requirements and the constant struggle to build shared understanding. They gave practical tips for breaking down silos and making modeling sessions actually work - not just as visual exercises, but as real opportunities for teams to learn together.

In this episode, I talk to Ben Linders about what really drives team autonomy and effective software development. We get into team culture, the importance of psychological safety, and why diversity matters - not just as a feel-good topic, but as a genuine catalyst for change. Ben shares practical tips from his workshops, discussing how teams can move from being stuck to taking meaningful action. We discuss, how to avoid that sticky notes from retrospectives gather dust and how to make results visible, keeping actions manageable, and introducing a little bit of fun through gamification.

In this episode, I talk to Lisa Crispin about holistic testing and what it really means for teams striving for better software quality. Lisa brings her experience to the conversation, sharing how testing is much more than a stage or a checklist - it’s a mindset that weaves through every part of the development process. We dig into the practical side: how teams can focus on both internal and external quality, the value of strong relationships, and the power of good questions. It’s clear: true quality comes from collaboration and curiosity, not just tools or process. There’s a lot for teams to rethink here.

In this episode, I talk to Kari Kakkonen about his Act 2 Lead model and why testing leadership is often missing in software testing. We unpack the reality that while grassroots testing within teams works well, the higher levels of organizations often lack a real understanding and leadership around quality. Kari lays out his model, a memorable eight-letter heuristic, as both a guide and a checklist for leaders at any level. It made me reflect on how companies approach testing - sometimes leaving it solely to autonomous teams but missing the big picture. I found myself wondering: is strong leadership the missing link for better quality software?

In this episode, I talk with Rik Marselis about the world of test design techniques. We go into why many testers struggle to apply the methods they learn, despite their potential to enhance quality assurance. Rik shares insights on how to select the right technique for different testing scenarios, emphasizing the need for a balanced approach that combines structured methods with experience-based testing. He introduces four key groups of test design techniques and illustrates how templates and real-life examples can make these concepts more applicable. I hope this conversation inspires you to integrate effective testing techniques into your practice, reminding us that quality is ultimately a deliberate choice.

In this episode, I talk with Isabel Evans about breaking stereotypes in the IT and testing industries. We go into the common misconceptions about testers, like the idea that they are mostly quiet, socially awkward individuals. Isabel shares her research findings, revealing that testers come from a wide array of backgrounds, including acting and arts. We discuss how this diversity enriches the field and challenges current hiring practices. The conversation opens up new perspectives on creating more inclusive environments in tech, prompting us to rethink who we see as a good fit for these roles.

In this episode, I talk to Kevlin Henney to explore the future of software engineering. We go deep into timely topics like artificial intelligence, the evolving role of developers, and the skills that will matter most in the years to come. Kevlin shares his perspective on how the industry may change—and why understanding people could be even more important than mastering tools. With his insightful thoughts on coding languages and ethical considerations in AI, he challenges us to think critically about what lies ahead. Join us for a thought-provoking conversation that will make you rethink your approach to technology and collaboration in the workplace.

In this episode, I speak with Szilárd Széll about the transformative role of AI in software testing and business processes. Szilárd, a notable figure in the testing community, shares valuable insights on the challenges and opportunities that come with integrating AI agents into our workflows. We explore the pressing questions surrounding trust in AI, how it can enhance business agility, and the necessity for testers to adapt their strategies in this evolving landscape. With the rise of AI, we need to rethink our approaches to quality assurance, balancing innovation with caution. As Szilárd suggests, engaging closely with AI can amplify our capabilities and drive progress.