A quality engineering playbook serves as an adaptable framework combining principles, tools, and real-world implementations, evolved over a decade to improve QA across diverse teams. The discussion highlights community-driven conferences, automation of repetitive tasks, and collaborative innovation to advance testing practices and team motivation.

Quality Blether

Quality Blether is the official podcast of the Scottish Testing Group. Episodes are guest interview based.

• https://shows.acast.com/quality-blether

Episode Details

• Show Notes: https://scottishtesting.org/
• Published: 2026-04-17T21:28:14Z
• Duration: 6:36
• Author: Unknown

Overview

The podcast explores the concept of a quality engineering playbook, described as a structured framework akin to a “recipe” that combines foundational principles, tools, and context-specific implementations. This approach, developed over a decade, has been applied across varied teamsfrom enterprises to startupswith the goal of fostering systematic improvements in quality assurance. Emphasis is placed on adaptability, with the playbook evolving through continuous feedback and real-world application.

A significant focus is on community-driven conferences like Testing Pairs, which prioritize inclusive participation by encouraging collaboration between experienced and novice attendees. Peer feedback is highlighted as a core value, enabling iterative refinement of ideas in line with quality engineering’s principles of continuous improvement. Additionally, the discussion stresses the importance of automation in modern testing practices, advocating for automating repetitive or “painful” tasks rather than relying on regression testing. This shift aims to break bottlenecks and enhance efficiency in software development workflows.

The podcast also touches on passion and collaboration within quality engineering, celebrating the energetic and collaborative spirit of events that drive innovation. The playbook itself is framed as a dynamic, “evergreen” document, continuously updated to reflect evolving practices. Highlighting the influence of figures like Lisa Gerard and Janet Gregory, the content underscores a broader movement to inspire and motivate teams toward adopting more effective, adaptable quality strategies.

What If

• What if you built a quality engineering playbook tailored to your business context, starting with one automated pain point?

  • Move: Identify a repetitive, error-prone task (e.g., deployment checks, CI/CD validation), automate it using existing tools, and document the process as part of your playbook.
  • Why_now: The shift to automation over regression testing is urgent; fixing bottlenecks now reduces long-term technical debt.
  • Expected_upside: A scalable, repeatable process that improves reliability, freeing time for strategic work while serving as a foundation for a living playbook.

• What if you hosted a virtual peer feedback session with fellow developers to refine your testing strategies?

  • Move: Schedule a 60-minute async video call with 23 peers, sharing your current testing automation workflows and inviting real-time feedback.
  • Why_now: The Testing Pairs conferences peer feedback model is proven to accelerate idea refinement; solo operators often lack this external input.
  • Expected_upside: Updated automation practices that align with community-driven best practices, validated by external perspectives.

• What if you restructured your testing priorities to focus on automating manual data validation workflows instead of regression suites?

  • Move: Audit your current regression tests, identify those that duplicate manual checks, and replace them with scripted data validation tools (e.g., JSON schema validators).
  • Why_now: The text emphasizes automating painful tasks as a higher priority than regression testing; this reduces manual overhead and improves feedback loops.
  • Expected_upside: Faster test cycles, fewer false positives in testing, and measurable gains in developer productivity.

Takeaway

• Create a tailored Quality Engineering Playbook by documenting your foundational testing principles, tools, and processes, then layer in context-specific adaptations as your project scales.
• Prioritize automating repetitive or error-prone tasks over regression testing, identifying and scripting workflows that consume the most time or introduce frequent issues.
• Participate in community-driven events or online forums to exchange feedback with peers, ensuring your practices evolve through collaboration and diverse perspectives.
• Share your insights publicly (e.g., blogs, open-source contributions) to build influence and inspire others, aligning with the movement toward modernizing quality engineering practices.
• Regularly update your processes based on peer feedback, treating your quality framework as a living document that adapts to new tools, team needs, and industry trends.