The debate examines whether testing is a specialized discipline or a general skill, questioning QA’s role amid automation, AI, and evolving practices, while critiquing unsubstantiated claims about its necessity. It explores AI’s potential to aid testing but stresses the irreplaceable need for human judgment, adaptability, and collaboration in complex systems.

The Vernon Richard Show

The Vernon Richard Show - hosted by Vernon Richards and Richard Bradshaw. Usually a Testing themed discussion between Vernon and Richard. Official show notes have summary description, timestamped chapter headings, resource links. Show notes on the website sometimes have a full transcript. Released as audio and video.

• https://thevernonrichardshow.com/
• https://www.youtube.com/@TheVernonRichardShow

Episode Details

• Show Notes: https://share.transistor.fm/s/1dd598ec
• Published: 2026-04-27T08:00:00Z
• Duration: 00:58:30
• Author: Vernon Richards and Richard Bradshaw

Overview

The podcast delves into the debate over whether testing qualifies as a specialized discipline or a general skill. It critiques assertions, such as those from influencers like Paul Hammond, that dismiss testing as a specialism without providing evidence, contrasting this with recognized roles like SRE or platform engineering. The discussion explores whether QA (Quality Assurance) should exist as a distinct role, referencing perspectives that question its necessity due to evolving practices, automation, and the rise of AI. Some argue that testing is a skill that doesnt inherently require a dedicated specialist, while others emphasize the need for expertise in complex scenarios. The episode also addresses historical biases against QA, often tied to outdated practices or underqualified testers, and questions whether modern systemsenabled by AI and automationwill render QA obsolete or redefine its relevance as a specialized function.

Another central theme is the evolving role of AI in software development and testing. The podcast speculates on how AI agents might handle testing tasks, though it highlights limitations in areas requiring judgment, such as selecting test cases or designing automation strategies. While AI could streamline routine testing, the discussion stresses that human expertise remains critical for nuanced decision-making and contextual understanding. This ties into broader debates about specialization versus generalist skills, with the argument that even as AI automates tasks, adaptability, domain knowledge, and cross-functional expertise will be essential. The episode also critiques the tendency of some professionals to make unsubstantiated claims about testing or other roles, emphasizing the need for evidence-based reasoning, critical thinking, and clarity in discussions about software practices. Finally, it raises questions about the future of roles like QA, suggesting that while traditional specialist roles may evolve, the underlying skill of testingand the need for strategic, cross-team collaborationwill persist in an AI-driven industry.

What If

• What if you redefine your testing role to align with AI’s capabilities, focusing on strategic oversight rather than routine tasks?

  • Action: Adopt AI tools for basic test case generation and execute them, reserving your time for designing test strategies, automation frameworks, and validating AI outputs.
  • Why Now: AI is advancing rapidly, and the industry is shifting toward automation; routine testing tasks are becoming commoditized, while strategic oversight remains critical.
  • Expected Upside: Increased efficiency in test coverage, allowing you to focus on high-impact areas like system resilience, edge cases, and cross-team knowledge sharing.

• What if you start integrating AI tools into your testing workflow but also invest in cross-training in DevOps and coding to stay relevant?

  • Action: Select an AI-powered testing tool (e.g., AI test case generator) for basic tasks, then learn DevOps practices (CI/CD pipelines) and foundational coding to better understand system integration points.
  • Why Now: AI is becoming standard, and cross-functional skills are in demand; developers who can bridge testing, coding, and automation are more valuable in complex systems.
  • Expected Upside: Ability to contribute to full-stack solutions, reducing dependency on specialized testers and positioning you as a versatile problem-solver.

• What if you launch a micro-course on testing for developers, combining AI usage with strategic testing principles, to position yourself as a go-to expert?

  • Action: Create a 10-lesson course covering AI-driven testing tools, critical thinking in test design, and storytelling to communicate testing value, then promote it via YouTube or LinkedIn.
  • Why Now: Theres growing demand for educators who bridge AI and testing; the market lacks clear guidance on leveraging AI as a complement, not a replacement, for human expertise.
  • Expected Upside: Establish authority in the space, attract clients or collaborators, and generate passive income while addressing a market gap.

Takeaway

• Enhance your communication skills to articulate testing value: Actively practice storytelling and documentation to showcase the impact of your testing expertise, ensuring stakeholders understand your role beyond basic task execution. This addresses the critique of poor communication and undervaluation of testing.

• Invest in automation and AI tool proficiency: Prioritize learning automation frameworks and AI-driven testing tools (e.g., LLMs) to stay competitive. Use them to handle repetitive tasks, freeing time for higher-level critical thinking, as discussed in the context of AI’s evolving role in testing.

• Develop a hybrid skill set of testing, coding, and coaching: Broaden your expertise beyond narrow specialization by combining technical coding skills with testing knowledge and leadership abilities (e.g., mentoring, process improvement). This aligns with the trend of “skill stacking” to remain adaptable in an AI-driven industry.

• Articulate your unique value proposition in testing: Clearly define why your testing approach adds value compared to AI agents or average practitioners. Document use cases, explain decision-making rationale (e.g., test design choices), and share results to justify your role in the face of automation challenges.

• Engage with community debates to refine your perspective: Actively participate in discussions with influencers (e.g., on LinkedIn or forums) to explore critiques of testing as a specialism. This helps clarify your stance, fosters collaboration, and ensures your practices stay aligned with industry trends and challenges.