SmartBear leverages AI to enhance API management and testing tools, addressing gaps in software quality caused by rapid tech shifts and outdated workflows, while emphasizing collaboration and intent validation in QA processes. The discussion highlights the need for flexible strategies in AI integration, balancing innovation with legacy systems, governance, and systemic risk management in enterprise solutions.

Into The MoTaverse

Rosie Sherry interviews people involved in testing. Video only interviews. Available on youtube or the homepage. Each episode has a full transcript if you find it on the main site.

• https://www.ministryoftesting.com/podcasts/into-the-motaverse
• https://www.youtube.com/playlist?list=PLbdLjg29s9lCY4hspzj3AGdAL7Vr2ys1B

Episode Details

• Show Notes: https://www.youtube.com/watch?v=TppVNUhKc2g
• Published: 2026-06-03T16:12:23Z
• Duration: 01:03:52
• Author: MoTaverse

Overview

The podcast explores SmartBear’s role as a software company specializing in API lifecycle management tools (e.g., Swagger, Spectral) and application testing solutions (e.g., Zephyr, Qmetry), with recent development of AI-driven testing innovations. Leadership under Dan Faulkner emphasizes streamlining product portfolios, integrating acquired technologies, and addressing market needs through both internal innovation and strategic acquisitions. The discussion delves into the evolving impact of AI on open-source projects, noting a divide between companies adopting closed-source models and those, like SmartBear, maintaining open-source contributions while operating commercially. It also highlights challenges in balancing rapid technological changessuch as increased reliance on APIs and automationwith the need for secure, scalable enterprise solutions.

Key themes include the accelerating pace of AI adoption, which is outpacing historical tech shifts, creating friction between developers and QA teams due to outdated workflows and unclear AI implementation. The podcast underscores growing quality gaps in software development, where expedited coding and unit testing create bottlenecks in downstream testing, risking security and governance issues. Solutions proposed include fostering collaboration between coding and non-coding roles, redefining QA responsibilities to prioritize intent validation, and leveraging tools like BearQAI-driven agents that automate testing, defect detection, and reporting. The discussion also addresses the importance of context-driven decision-making, the need for intent validation in AI outputs, and the potential of knowledge graphs to improve systemic understanding across teams.

The podcast further examines the evolving role of QA professionals, who are increasingly involved in early-stage development and benefit from natural language-based automation tools. It critiques rigid tech purist approaches, advocating for flexible strategies that account for legacy systems and business context. Challenges around AIs long-term impact, including job displacement fears and the need for cross-functional empathy, are noted, alongside calls for innovation in automation to alleviate workforce strain. The summary highlights SmartBears focus on improving quality assurance through AI integration, emphasizing the necessity of aligning technological advancements with user needs, governance, and systemic risk management.

What If

• What if you integrate BearQs AI agents into your testing workflow to automate QA tasks that would otherwise require manual effort?

  • Move: Deploy BearQs testing agent to automatically generate end-to-end tests, API tests, and detect defects in your application.
  • Why Now?: Rapid AI adoption demands efficient QA practices, and BearQs agents can handle repetitive tasks, freeing you to focus on complex edge cases and user-centric testing.
  • Expected Upside: Reduce manual testing time by 4060%, ensure consistent test coverage, and align with SmartBears AI-driven testing strategy to future-proof your project.

• What if you adopt knowledge graphs to model your applications system behavior for better risk identification and collaboration?

  • Move: Use a knowledge graph tool (e.g., based on SmartBears open-source.swagger principles) to map application pathways, dependencies, and user roles.
  • Why Now?: The rise of AI agents like BearQ requires aligning human intent with system behavior, and knowledge graphs help QA and developers identify gaps in requirements or security permissions.
  • Expected Upside: Improve cross-team communication, reduce critical bugs from misaligned permissions or access logic, and create a shared framework for QA, dev, and security teams.

• What if you create a hybrid QA framework blending AI automation with human oversight to balance speed and accuracy?

  • Move: Implement BearQs reviewer role by setting up a process where AI-generated tests are validated by you for intent alignment and edge-case prioritization.
  • Why Now?: Concerns about AI agents making unsolicited design decisions (e.g., unrequested features) highlight the need for intent validation, as noted in SmartBears discussions on agent-driven testing.
  • Expected Upside: Maintain high-quality standards through human judgment while scaling testing efficiency, ensuring your application meets both functional and user-experience goals.

Takeaway

• Phase Out Underused Tools Strategically: Regularly assess the usage and relevance of your software tools. Discontinue tools with declining adoption by providing advance notice to users, ceasing new sales, and offering a transitional support period to minimize disruption (as SmartBear does with older products).

• Invest in In-House AI-Driven QA Tools: Develop internal tools like AI agents (e.g., BearQ-style “exploration agents”) to automate repetitive tasks such as test creation, defect detection, and application exploration, freeing QA teams to focus on high-value, intent-validation work.

• Automate End-to-End Testing with Natural Language Integration: Adopt low-code/no-code platforms that support natural language inputs (e.g., BearQ’s ability to rewrite tests in plain language) to reduce manual test creation while improving test coverage and collaboration with non-technical stakeholders.

• Prioritize Cross-Functional Collaboration: Foster communication between developers, QA teams, and product stakeholders to align on goals, resolve ambiguity, and avoid workflows that prioritize speed over quality (e.g., using knowledge graphs to model system understanding and prevent misaligned agent decisions).

• Leverage Open Source for Core Components, Commercialize Enhancements: Maintain open source projects for foundational tools (e.g., Swagger) but build commercial value through premium features, support, and AI-driven extensions that address enterprise scalability and security needs (as SmartBear does).