Monthly Recap
The bigger picture
June 2026
June's throughline was consolidation, not invention: existing E2E and load-testing tools absorbed features that used to require a separate product, while the eval-writing trend from Q2 hardened into a named job duty.
Testing tools are absorbing adjacent categories
Performance, contract testing, and self-healing locators all moved from standalone products into features of existing E2E runners this month.
Eval-writing became a stated QA duty
Multiple surveys and case studies independently confirmed the same shift: writing and maintaining LLM evals is now counted as core QA work, not an AI-team side project.
CI infrastructure is quietly getting greener metrics
Several CI providers shipped per-run sustainability estimates, a signal that carbon reporting is becoming a default dashboard column rather than an opt-in add-on.
- engineeringGitHub Changelog
GitHub Actions adds per-job carbon estimate in run summaries
CI runs now surface an estimated CO2e figure next to duration and cost.
- github-actions
- sustainability
- test automationSD Times
Testim and Mabl both add 'self-healing' diff explanations
Both platforms now show a plain-language reason for why a locator was auto-updated.
- self-healing
- low-code