Tester Influence: Frame Bugs by Business Impact
Tester influence is influence without authority: frame each finding for its audience. A 15-second check at standup does more than a big program.
Software Testing Unleashed : Page 4 of 4
Latest Episodes
Learn from global testing leaders and innovators.
Cypress to Playwright: Migrate Critical Paths First
Switching test automation frameworks mid-product is messy, yet a Cypress to Playwright move works. Pricing forced it, AI translated the tests.
Cross-Functional Teams Need a Clear Owner for Quality
In cross-functional teams, when everyone owns quality, no one really does. Why these teams lack deep testing skills and how testers still add value.
Nonviolent Communication in Testing: Observe, Don't Judge
Nonviolent communication gives testers four steps: observation, feeling, need and request. It lets QA teams raise hard points without blaming anyone.
Teaching Test Automation: Hands-On Labs Before Theory
Teaching test automation in Vilnius starts with scripts, APIs and performance tests. Test plans come later, once students have seen systems break.
Resistance to Change: Turn Skeptics into a Resource
Resistance to change targets the process more than the idea. Skeptics spot risks that advocates miss, and questions move people more than data.
Built-In Quality: Small Practices Beat Big Frameworks
Built-in quality often breaks not in the team but one layer above, in management. How small practices, not frameworks, keep quality from slipping.
When Property-Based Testing Pays Off, and When It Doesn't
Property-based testing generates test cases from a specification and found a 17-step LevelDB bug. It gets costly when every test run is billed.
Security by Design: Why Custom Encryption Adds Risk
Security by design starts with threat modeling any team can run, layered defenses and secure defaults. Security bolted on in the last 10% stays thin.
Collaborative Software Design: Surface Assumptions Early
Collaborative software design puts developers, testers, architects and business experts around one model. Event storming exposes hidden assumptions.
Team Autonomy: How Teams Solve Problems Together
Team autonomy grows when teams solve problems together. Psychological safety makes that possible, but one careless remark can undo weeks of work.
Holistic Testing: Quality Work at Every Stage of the Loop
Holistic testing makes the whole team own quality, with testing at every stage of the DevOps loop. Shared understanding early prevents costly rework.
Leader in Software Testing: Eight Principles from ACT2LEAD
A leader in software testing builds a quality culture. The ACT2LEAD model gives eight principles, from transparency to risk and diversity.
Choosing Test Case Design Techniques: About Ten Are Enough
Most testers know test case design techniques but rarely use them. Four groups, five techniques, and the right selection logic change that.
IT Stereotype: Only 6% of Surveyed Testers Match It
Only 6% of testers fit the classic IT stereotype. Arts graduates, boat builders, urban planners: the data on who actually does testing reframes how we recruit.
AI Code Generation: More Legacy Code, Produced Faster
AI code generation pushed up code churn and duplicates on GitHub by early 2024. Testing, precise questions and fundamentals set developers apart.
AI Agents in Software Testing: Treat Them like New Hires
AI agents in software testing need what a new hire gets: a selection process, a probation period, and ongoing performance checks, not fixed outputs.
25 Years of Software Testing: The Pendulum Swings Again
Over 25 years of software testing, the tester swung from separate specialist to quality coach in the team. Now AI makes quality everyone's job.