A holistic approach to software testing is emphasized, blending continuous collaboration across roles to address technical and user-centric challenges while adapting Agile practices meaningfully. The evolving role of testers as quality engineers underscores the need for cross-disciplinary knowledge, balanced automation, human judgment, and community-driven practices to ensure sustainable, user-aligned outcomes.

How To Test This?

interview episodes where Mamadou N’diaye talks with with software testing experts

• https://podcasters.spotify.com/pod/show/spidey1944
• https://www.youtube.com/@HowToTestThis
• https://www.linkedin.com/in/mamadou-ndiaye-consultant/

Episode Details

• Show Notes: https://podcasters.spotify.com/pod/show/spidey1944/episodes/How-To-Test-With-An-Holistic-Approach--Lisa-Crispin-e3ikdo0
• Published: 2026-04-29T03:29:57Z
• Duration: 00:54:21
• Author: Mamadou N’diaye

Overview

The podcast discusses strategies for effective software testing, emphasizing a holistic approach that integrates testing across all stages of development. It highlights the importance of team collaboration, where developers, testers, and stakeholders collectively address technical and non-technical aspects like user experience and documentation. Key principles include continuous testing throughout development, fostering inclusivity by involving all team members in quality assurance, and adapting Agile practices to fit project dynamics. The discussion critiques superficial Agile adoption, such as rigid processes or ritualistic stand-ups, and instead advocates for a focus on sustainable value delivery and trust-based collaboration.

The role of testers is evolving from traditional roles to that of quality engineers or consultants, emphasizing coaching, shared understanding, and risk management. The conversation underscores the need for cross-disciplinary knowledge, balancing specialized expertise with generalized awareness of tools and concepts to improve communication. Challenges like over-reliance on automation or AI are addressed, with a call for maintaining human judgment in testing to avoid devaluing critical roles. The podcast also stresses the importance of psychological safety, iterative testing, and user-centric practices to ensure alignment with customer needs and long-term quality.

Future trends include the necessity of adaptability, continuous learning, and leveraging AI to enhance efficiency while preserving the irreplaceable value of human-led exploratory testing. The discussion emphasizes early risk assessment, iterative improvements, and fostering trust within teamsdrawn from personal anecdotes like working with donkeysto achieve sustainable outcomes. Addressing systemic issues like burnout and workload management is also highlighted, alongside the importance of community-driven learning and collaboration to advance quality practices.

What If

• What if you integrated exploratory testing into your coding workflow as you write code?
  Concrete move: Pair exploratory testing with your development process by writing tests immediately after each code increment.
  Why now: Early detection of edge cases prevents rework and aligns with XP principles of continuous feedback.
  Expected upside: Reduces technical debt and improves code robustness, freeing time for higher-level design decisions.

• What if you created a trust-based collaboration loop with a peer or mentor to simulate the “donkey” metaphor?
  Concrete move: Schedule weekly check-ins with a peer to co-design test scenarios and review each other’s work.
  Why now: The donkey analogy emphasizes trust over coercionthis ensures peer accountability and shared ownership of quality.
  Expected upside: Accelerates learning, reduces blind spots, and builds a culture of mutual support for sustainable collaboration.

• What if you automated regression testing with AI tools to free time for human-led testing?
  Concrete move: Deploy an AI-driven regression test generator (e.g., using tools like Testim or Applitools) to cover routine checks.
  Why now: The text highlights automations role in freeing time for exploratory testing and reducing monotony.
  Expected upside: Faster feedback loops for core features, enabling deeper focus on user-centric testing and risk prioritization.

Takeaway

• Integrate testing early and continuously into your development process, treating it as a collaborative responsibility rather than a final step. Use small-batch development and tools like feature flags to test in production safely and iteratively refine quality.

• Prioritize non-technical testing considerations, such as user experience, accessibility, and documentation, alongside technical aspects. This ensures your product meets both functional and user-centric quality standards.

• Engage stakeholders and end-users early to align on requirements and avoid rework. Use techniques like example mapping or impact maps to clarify expectations and validate assumptions before coding begins.

• Adopt continuous learning and adaptability by staying updated on evolving testing methodologies, tools (e.g., AI-assisted testing), and domain-specific knowledge. Allocate time weekly for learning through resources like Test Automation University or community forums.

• Reduce rework by aligning development with business goals using risk-based prioritization. Collaborate with product stakeholders to identify key quality attributes (e.g., security, performance) and focus testing efforts on high-impact areas.