Welcome to Issue #3!
Contract testing is quietly becoming the topic nobody can avoid in microservices teams. Visual testing vendors are all shouting “AI” but most are still doing pixel diff. And Playwright 1.61 is in daily alpha builds. Busy week.
Happy testing! 🙂
NEWS
Playwright 1.61 Alpha Done, 1.62 Alpha Already Shipping
Alpha builds for 1.61 have been shipping every day since late May. Stable 1.60 is still latest on npm but the pace of alpha commits shows the team isn’t slowing down. Worth watching the changelog if you’re planning a framework upgrade cycle. The 47M weekly download figure confirmed this week is also a useful number to have if you’re still convincing stakeholders why Playwright deserves investment.
Visual Testing in 2026: Everyone Says AI, Most Are Still Doing Pixel Diff
Good honest write-up from Virtuoso QA cutting through the noise. Most tools calling themselves “AI visual testing” are still doing pixel-by-pixel comparison with a thin ML layer on top, which means false positives from font rendering and anti-aliasing still burn your time. Genuine AI visual testing understands what elements mean, not just what pixels changed. The gap between the two is bigger than most vendor pages admit.
Contract Testing Is Having a Moment and the Framing Finally Makes Sense
Best opening line I’ve read in a testing blog in months: “Two teams ship on the same day. Tests go green on both sides. Then staging blows up because a field got renamed.” That’s exactly the gap Pact contract testing fills. Not a replacement for your E2E suite. It’s the piece that catches API mismatches neither unit tests nor integration tests can see.
AUTOMATION
Playwright HTML Report Timeline: See Where Test Time Actually Goes
Shivam Bharadwaj’s breakdown of the Timeline view in Playwright 1.58’s Speedboard tab is the clearest write-up on this feature I’ve found. Slow suites rarely fail loudly, they just get more expensive. This view shows exactly where time is going across your test run. I’ve seen teams shave 20-30% off suite runtime just by looking at this for the first time.
Pact in Node.js: Consumer Tests, Provider Verification, CI Integration
Clean hands-on guide covering the full Pact workflow in Node.js, consumer test writes the contract, provider verifies it, Pact Broker stores and versions it, can-i-deploy gates your release pipeline. The part on using matchers instead of exact values is worth reading carefully. Exact value matching is how contracts become fragile.
TOOLS & GITHUB
testzeus-hercules: Open Source Testing Agent, No Code, 1K Stars
Kudos to the TestZeus team for keeping this genuinely open source. Hercules turns Gherkin steps into automated UI, API, security, accessibility, and visual tests without writing code. Runs on OpenAI, Anthropic, Llama, and Mistral. Outputs JUnit XML and HTML reports. Updated May 26, 2026. Worth watching if you’re evaluating agentic testing tools and don’t want vendor lock-in.
jmeter-java-dsl: Write JMeter Tests in Code, Not XML
If you’ve ever tried to version control a JMeter .jmx file you know the pain. Abstracta’s JMeter Java DSL lets you write performance tests as plain Java code, run them with JUnit, and commit them like any other test file. No GUI, no XML bloat, no merge conflicts on test plans. 100K+ downloads globally and actively maintained. Worth knowing about if your team uses JMeter and wants it to fit better into a CI pipeline.
Applitools Eyes 10.22 Adds Storybook Addon and Figma Plugin
Two additions worth knowing about. The Storybook addon brings component-level visual testing directly into your design system workflow. The Figma plugin lets designers compare production screenshots against their Figma specs without involving a developer. Both close gaps that have been annoying design-heavy teams for a while.
bug0.com 🔗
COMMUNITY INSIGHT
Making the QA to SDET Jump in 2026: What Skills Actually Matter Now
Ayushi Malviya’s write-up covers the career shift honestly. The point that stuck with me: 58% of enterprises are actively upskilling QA teams in AI tools right now, so this isn’t a “future skill” conversation anymore. The practical advice on building programming foundations before jumping into AI tools is exactly right. Too many testers try to shortcut that step and it shows.
Is Contract Testing Worth the Overhead for Small Teams?
Good debate picking up this week. TotalShiftLeft argues contract testing is the most important infrastructure investment a microservices org can make. But I keep hearing from teams under 20 engineers that the Pact Broker setup and cross-team coordination cost more than the problem it solves at their scale. Both sides have a point. The answer probably depends on how independently your services actually deploy.
PRACTICAL TIP
Use Matchers in Pact, Not Exact Values
When writing Pact consumer tests, never assert exact values for things like IDs, timestamps, or generated strings. Use like() to match by type and eachLike() for arrays. Exact value matching makes your contracts brittle and breaks on perfectly valid data changes from the provider. One of those things that bites every team the first time and feels obvious in hindsight.
VIDEOS
Appium 3: Architecture, Features and Migration (Full Webinar)
TestMu AI engineers walk through Appium 3 installation, server flags, deprecated endpoints, gesture APIs, and live migration from Appium 2. More thorough than most written guides on this right now. Good watch before you start any Appium 2 to 3 upgrade.
Demo: Using AI for Visual Regression Testing
Mike Herchel demos a custom AI visual regression tool he built and uses in production. Worth watching alongside this week’s visual testing article. Seeing what a real practitioner built vs what vendors sell is a useful
comparison. Short, practical, no marketing.
OPEN QUESTION
Posted this on r/Playwright this week after using AI tools for a few months. Some days it feels like a
superpower. Other days I’m spending more time fixing what the AI generated than I would have spent just
writing the test myself.
Last week I reviewed a suite where half the tests had no real assertions. Just “expect page to be visible”
type stuff. Technically passing. Completely useless. Am I using it wrong? Curious what others are actually
experiencing. manual testers too, not just automation.
→ Join the discussion on Reddit
And Finally…
Three conversations this week where someone described their “AI-powered test suite” and then mentioned they haven’t looked at what the tests actually assert. That’s not AI testing. That’s automation theater with extra steps. 😅
