Welcome to Issue #4!
Postman’s March pricing change quietly pushed a lot of teams to look at alternatives. Performance testing is getting serious attention as a CI/CD gate. And accessibility compliance is moving from “good idea” to “legal requirement” faster than most teams are ready for. Busy week.
Happy testing! 🙂
NEWS
Accessibility Testing in 2026: WCAG 2.2 Is the New Standard, EAA Enforcement Has Started
Joe Colantonio gathered five accessibility experts for this one including a senior analyst at Salesforce and a quality engineering manager at EasyJet. Short version: automation catches 20-57% of accessibility issues. The rest still needs humans. WCAG 2.2 AA is now the global benchmark. European Accessibility Act enforcement started mid-2025 and teams that haven’t wired accessibility into CI are starting to feel the compliance pressure in a real way.
testguild.com 🔗
Postman Killed Free Team Plans in March. Bruno Hit 41K Stars and Is Growing Fast
Postman’s March 2026 pricing change pushed teams to $14-49 per user monthly or out the door. Bruno is the clearest beneficiary. Open source, Git-native, stores API collections as plain .bru text files in your repo, requires no account or internet connection. 41,700 GitHub stars, MIT licensed, completely free for teams of any size. Migration from Postman takes a weekend and mostly just works.
byteiota.com 🔗
Gartner: 40% of Enterprise Apps Will Have Task-Specific AI Agents by End of 2026
Up from less than 5% in 2025. Katalon’s June 8 guide is a grounded read alongside that stat. Most teams sit somewhere between AI-assisted testing and early agentic QA, not fully at either end. The distinction that matters when evaluating tools: goal-directed agents that plan and adapt are genuinely different from AI-assisted scripting with autocomplete. Vendors blur this constantly and the Gartner number gives them cover to blur it even more.
katalon.com 🔗
AUTOMATION
Docker Compose for E2E Test Environments: Full Stack, One Command
Half of E2E test failures are environment differences, not actual bugs. One developer on PostgreSQL 15, the CI runner on 16. Docker Compose fixes this by defining your entire stack in one YAML file. Every developer and CI runner gets the exact same environment. The guide covers service dependencies, health checks, and the common pitfalls that make E2E testing painful before you even run a test.
oneuptime.com 🔗
Load Testing in 2026 Is No Longer Optional for Any Team Serving 100+ Concurrent Users
ARDURA’s June guide makes the case clearly. Cloud cost discipline and SLO-based engineering both demand quantitative evidence about capacity, not guesses. The four test types are worth knowing by name: load, stress, soak, and spike. Each catches different failure modes. Teams that run only load tests and skip soak testing are the ones who discover memory leaks two weeks after a release.
ardura.consulting 🔗
API Testing Tools in 2026: The Complete Practical Guide
Keploy’s May guide covers the full landscape without the usual vendor bias. The framework that actually helps: if you want to stop writing and maintaining API tests manually, Keploy captures real traffic. If you want BDD-style readable tests, Karate. If you need Java/JVM enterprise, REST Assured. If you need API security scanning in CI, OWASP ZAP via Docker. One question, one tool. Worth reading before evaluating anything.
keploy.io 🔗
TOOLS & GITHUB
usebruno/bruno: Git-Native API Client, 41K Stars, Completely Free
Collections stored as plain .bru text files in your repo. Every API change shows up in a Git diff. Review in PRs, roll back when something breaks, no proprietary cloud format. The CLI (@usebruno/cli) runs collections in CI with JUnit XML output. Works in GitHub Actions, GitLab, Jenkins, anything. No account, no internet required. Kudos to the Bruno team for keeping this genuinely free with no paid tiers.
github.com 🔗
alumnium-hq/alumnium: AI Layer for Selenium, Playwright, and Appium
Built by Alex Rodionov, Airbnb engineer and Selenium project tech lead. Sits on top of your existing framework, no rewrite needed. Write al.do(“search for playwright”) instead of maintaining selectors. Works with OpenAI, Anthropic, and other LLM providers. Also ships as an MCP server: claude mcp add alumnium. Active development, cross-framework, open source.
github.com 🔗
dequelabs/axe-core: The Engine Underneath Most Accessibility Tools in 2026
v4.11.4 shipped April 2026. Powers Lighthouse, Cypress Accessibility, Playwright’s built-in accessibility testing, and axe DevTools. Most accessibility products in 2026 run axe-core underneath with a UI layer on top. Worth knowing this before you evaluate any accessibility tool — it changes how you read the feature comparisons and price differences between them.
github.com 🔗
COMMUNITY INSIGHT
70% of Teams Have No Formal Test Data Strategy. That Number Explains a Lot of Flakiness
TotalShiftLeft’s April 2026 guide opens with the stat and I believe every word of it. Every team I’ve reviewed this year has some version of the same problem: test data provisioned manually, inconsistently, sometimes copied from production with PII still in it. Poor test data accounts for roughly 40% of automation failures. That’s not a tooling problem, that’s a process problem nobody has prioritised.
totalshiftleft.com 🔗
Making the QA to SDET Jump in 2026: What Skills Actually Matter Now
Ayushi Malviya’s write-up covers the career shift without the usual LinkedIn optimism. The stat worth keeping: 58% of enterprises are actively upskilling QA teams in AI tools right now. The practical advice on building programming foundations before jumping to AI tooling is exactly right. Too many testers try to shortcut that step and the gap shows up six months later when they’re maintaining AI-generated tests they can’t debug.
quashbugs.com 🔗
PRACTICAL TIP
Use Docker Compose Health Checks Before Running Any Tests
Add healthcheck to every service in your docker-compose.yml and use depends_on: condition: service_healthy for your test runner container. Without this, your tests start before the database is ready and you get flaky failures that look like test bugs but are actually race conditions. One of those things that takes 10 minutes to add and saves hours of debugging every few sprints.
VIDEOS
Stop Rewriting Tests: AI for Selenium and Playwright Without Starting Over
TestGuild, May 6, 2026. Alex Rodionov demos Alumnium live. The section where the same test survives a UI redesign without touching a selector is the most convincing AI test maintenance demo I’ve seen this year. Worth watching if you’re on a Selenium team weighing migration costs against AI tooling costs.
testguild.com 🔗
Bruno CLI + GitHub Actions: Run API Tests in CI and View HTML Reports
Takes a Bruno collection, runs it from the command line with Bruno CLI, and wires it into GitHub Actions with HTML report output. Exactly what you need if you’ve switched from Postman to Bruno and want it running in CI. Short, practical, no fluff.
youtube.com 🔗
This Week’s Discussion
Posted this on r/QualityAssurance this week because I kept seeing the same thing across teams I’ve worked with. Some create dummy data, some mask production data, and some are still running tests against a direct copy of production with real PII sitting in there.
Curious what’s actually happening in real projects. Do you treat test data as seriously as production data, or is it still a “grab something and start testing” situation?
→ Join the discussion on Reddit
And Finally…
Had a conversation this week where someone said their team “does accessibility testing” and meant they run Lighthouse once before release. That’s not accessibility testing. That’s a screenshot of a score. The European Accessibility Act doesn’t care about your Lighthouse score. 😅
