DiscoverSoftware Testing Unleashed - QA, DevEx & Quality Engineering
Software Testing Unleashed - QA, DevEx & Quality Engineering
Claim Ownership

Software Testing Unleashed - QA, DevEx & Quality Engineering

Author: Richard Seidl | Software Development & Testing Expert

Subscribed: 72Played: 731
Share

Description

Software testing is no longer just a phase—it’s the foundation of modern engineering and your ultimate competitive advantage.

Welcome to Software Testing Unleashed, the weekly podcast for anyone dedicated to building better software, faster. Hosted by Richard Seidl, renowned expert in software development and testing, this show is your backstage pass to the tools, tactics, and trends defining the next era of Quality Engineering.

Whether you are a QA Engineer, SDET, Developer, or Tech Leader, each week we bring you field-tested insights from the brightest minds in the software universe to answer the industry’s toughest questions:

- Smart Automation: When should you automate, and when is it a trap?
- AI & ML in Testing: How do you maintain quality in a world of non-deterministic code?
- The "How Much" Dilemma: How much testing is actually enough for your specific scale?
- Architecture & DevEx: What makes a great integration test and how do you improve developer experience?

From scaling QA strategies in enterprise projects to building your very first test suite, we bridge the gap between complex theory and practical execution. We dive deep into CI/CD, Cloud-native complexity, and the future of manual vs. automated testing.

🚀 Ready to unleash the next level of quality? Hit play, subscribe, and join a global movement of software professionals shipping with confidence.
80 Episodes
Reverse
GenAI evaluation turns into a question of better or worse once every answer a model gives could be correct, and that is where Deepshikha and Anamika Mukhopadhyay begin. We talk about why one model needs three different definitions of good as a customer bot, a clinical summarizer and a coding agent, and why most teams they meet in workshops measure whatever their tools give them by default. A faithfulness score like 0.87279 left a room of CXOs asking whether it was a rounding problem; a 12 percent drop in issue resolution and 200 extra tickets did not. And a prepared Reddit post shows how an indirect prompt injection slips past an agent that had blocked every direct one.
Contract-driven testing lets a tester work against a realistic mock instead of waiting for 50 integrated systems to behave, and that is what Phil Royston is bringing into a large bank. We talk about why mocks built on a developer's imagination produce unreliable tests, how agreed contract tests turn into mocks for API consumer and provider, and why the pitch to senior management fits on one slide while the middle managers hold the veto. Phil also explains why approved business requirements were not testable ones, what he means by parasitic end-to-end testing, and why his advice to any test manager is to wait for the crisis.
Building trust in teams starts with far smaller things than a team-building event, and that is what I talk through with Michael Kutz and Linda Van De Vooren. Michael brings Stephen Covey's waves of trust, from self-trust outward, and his rule that a kept promise about one issue in the code base is one of the Lego stones trust is built from. Linda talks about the inner critic she has practiced with for over ten years, about limitless honesty with a new client, and about why rest and fun come first. We also get into a 50,000 credit limit that became 500,000 through one extra zero, who owns the fix after that, and what makes an app trustworthy when it tells you what went wrong.
Mental skills keep testers thinking when AI offers to do it for them, and Ard Kramer puts it bluntly: you can't outsource your brain. With him I talk about why an idle brain loses its connections, how his cue HAH (human, AI, human) keeps the thinking on our side, and which four skills get a tester into the flow: goal setting, visualization, self-talk and stress control. Ard turns the test goal around, because one passing test confirms nothing, so his hypothesis aims at the moment the payment interface fails. He also explains the Zeigarnik effect, why an open task keeps your subconscious busy overnight, and why AI works best as a critical partner that asks you the questions.
Testing AI models means testing a magic box: nobody has the source code, and the behavior is neither controlled nor understood. Michael Bolton calls that strongly magical, and with him I talk about what follows from it. His principles are simple: if something matters very much, don't depend on magic, and if you use it anyway, responsibility demands that you test it and maximize testability. Simple output checks don't stand a chance against a language model, so testing becomes experiencing, exploring and experimenting, like peeling an onion. And Penn and Teller's clear plastic cups show why we fall for these models in the first place: the insight we see in their text comes from us.
loading
Comments