Episode 241: Bridges Smith from Smartbear
Categories: Podcasts , AB Testing
AI accelerates software development and testing, shifting roles from manual execution to strategic oversight, with tools like BearQ automating test creation and prioritization. Human judgment remains essential for validating AI outputs, while future advancements will integrate real-world usage data to enhance testing efficiency and quality.
AB Testing
AB Testing - Each episode is a chat between Brent Jensen and Alan Page with an occasional special guest.
Episode Details
- Show Notes: https://podcasters.spotify.com/pod/show/abtesting/episodes/Episode-241-Bridges-Smith-from-Smartbear-e3qocu0
- Published: 2026-10-19T15:29:45Z
- Duration: 00:48:01
- Author: AB Testing
Overview
The podcast discusses the transformative impact of AI on software development and testing, emphasizing how AI accelerates development cycles and changes the roles of developers and testers. As AI generates code and test cases at unprecedented speeds, testing must evolve to keep pace, shifting focus from manual execution to strategic oversight. AI-powered tools like BearQ help automate test creation, prioritize failures, detect non-functional issues, and eliminate redundant tests, improving efficiency and coverage. However, human judgment remains critical for validating AI outputs, ensuring quality, and maintaining visibility across complex systems.
A key theme is the need for specialized AI models and coordinated “agentic test teams” that can analyze diverse data sources - such as logs, requirements, and real user behavior - to make informed testing decisions. The discussion highlights the importance of systems thinking, where AI supports but does not replace human expertise in identifying bottlenecks, managing risk, and focusing on high-impact features. Future advancements will integrate customer telemetry and behavioral data to prioritize testing based on actual usage, while balancing automation with human accountability to ensure software correctness and deliver meaningful value.
What If
-
What if you built a specialized AI agent to triage and prioritize your bug reports?
- Move: Use an open-source LLM (e.g., Llama 3) to fine-tune a model on your past bug reports and telemetry data, then deploy it to automatically categorize and prioritize new issues based on severity, frequency, and user impact.
- Why Now?: With AI accelerating development cycles, manual triage is becoming a bottleneck - especially for solo developers drowning in noise from automated testing and user feedback.
- Expected Upside: Reduce time spent on issue sorting by 70%, surface critical bugs faster, and focus your limited development hours on high-impact fixes.
-
What if you automated the detection and removal of redundant tests in your suite?
- Move: Implement a script that analyzes test execution patterns and code coverage (using tools like Jest, pytest, or Playwright) to identify duplicate or overlapping tests, then use AI clustering to group similar behaviors and recommend pruning.
- Why Now?: AI can now generate thousands of tests quickly, but unchecked, this leads to bloated, slow suites - wasting compute and developer time during CI/CD.
- Expected Upside: Cut test execution time by 30 - 50%, reduce flakiness from overlapping logic, and improve feedback loop speed for solo development workflows.
-
What if you used real user behavior data to dynamically prioritize your test cases?
- Move: Instrument your production app with lightweight telemetry (e.g., via PostHog or Mixpanel) to capture top user flows, then build a cron job that syncs this data with your test runner to auto-adjust test execution order and frequency.
- Why Now?: Many solo developers test based on assumptions, not usage - leading to gaps in coverage where users actually struggle. AI makes it feasible to process real-world behavior at low cost.
- Expected Upside: Increase defect detection in critical paths by 40%, reduce wasted effort on unused features, and align QA directly with customer value.
Takeaway
- Integrate AI tools like BearQ or similar agentic QA systems to automate test creation, prioritize failures, and reduce manual effort in test maintenance and execution.
- Focus on customer telemetry and real usage data to identify high-impact testing scenarios and eliminate redundant or irrelevant test paths.
- Implement AI-driven redundancy detection to analyze and remove duplicate or overlapping test cases, especially when scaling test suites with AI-generated content.
- Adopt a human-in-the-loop workflow where AI proposes tests or bug fixes, but critical validation and prioritization decisions are made by humans to maintain quality and accountability.
- Use specialized AI models (not general LLMs) for tasks like code review, log analysis, and accessibility checks to improve accuracy and reduce noise in automated quality workflows.
For a PDF of longer Software Testing Podcast Episode Summaries with Briefing Notes and more detailed summary notes, visit EvilTester Patreon Podcast Summaries.