Systems | Development | Analytics | API | Testing

When teams use different programming languages, code becomes territorial. Your code. My code. Your problem. My problem. But when teams align on a single language, those barriers disappear. Suddenly, collaboration is effortless. Debugging isn’t someone else’s job—it’s everyone’s. As Selenium developers, every feature has to work across five languages. AI helps bridge the gap, but the real game-changer? A shared language that makes moving across the codebase seamless.

AI is being treated as a shortcut for quality. Is that a dangerous gamble? There are a few industry-wide experiments happening right now: Developers are being pushed to own quality, but without dedicated testers, gaps are forming. AI is being used as a crutch for testing, but can it actually replace critical thinking? The real risk? We won’t know how badly this approach fails until it’s too late.

The Test Tribe Calgary Meetup took place on 22nd January and featured David Paquette, Principal Software Engineer at Microsoft, who took us through the power of Playwright in making end-to-end testing seamless and reliable. If you've ever struggled with flaky tests, difficult test setups, or maintaining complex test code, this talk was packed with solutions. David demonstrated how to write stable cross-browser tests, debug efficiently using Playwright’s codegen, inspector, and trace viewer, and shared practical strategies to enhance test automation workflows.

AI isn’t a shortcut to perfect testing. It won’t magically fix your processes or write flawless code. But if used right, it will push testers and developers to think more critically. Instead of asking if AI should be part of testing, the real question is how to make it a true collaborator. That means: Using AI to highlight gaps, not blindly trusting its output Treating it as a thought partner, not an automation machine.