The biggest software testing developments in 2026 point to a more explicit, evidence-led discipline: IEEE has published an end-to-end automation standard, a model-based testing standard is still moving through final publication steps, and testing practitioners are giving more attention to AI quality, risk and traceability. These developments offer guidance and professional-learning options, not proof that automation or a credential guarantees better outcomes.
What’s new in software testing and test automation?
Three themes stand out: clearer standards for automation, a formal framework for model-based testing nearing publication, and growing attention to how teams evaluate AI systems and AI-assisted testing. The status of each development matters: an active standard, a standard under publication and a conference report are different kinds of news.
As an Amazon Associate I earn from qualifying purchases.
IEEE 3407-2025: an active standard for end-to-end automation tools
IEEE lists IEEE 3407-2025 as an active standard. Although “2025” appears in its name, IEEE says it was published on April 24, 2026, and received ANSI approval on August 26, 2026. It establishes minimum requirements for end-to-end software testing automation tools and provides guidance for preparing and performing automated testing in software integration environments, including streamlining development, execution and maintenance processes.
Free tools Windows power users keep installed
One-click scans. No signup required.
For teams, the practical point is that automation tooling can be evaluated against a stated set of requirements rather than treated solely as a collection of features. The standard describes guidance and minimum requirements; it does not establish that adopting a particular tool will improve a team’s results.
ISO/IEC/IEEE 29119-8: model-based testing standard under publication
ISO/IEC/IEEE 29119-8 covers requirements and guidance for applying model-based testing alongside the processes defined in 29119-2. ISO’s status page showed stage 60.00, “International Standard under publication,” on September 28, 2026. Final production steps were still underway on that date, so it should not be described as fully published without checking the current ISO status page.
The standard assumes automated generation of testware and test execution. It does not specify which model-based testing tools to select or how generation algorithms must be implemented. That distinction matters when using it to set expectations: it addresses requirements and guidance for applying the approach, not a prescribed toolchain or algorithm.
AI testing: quality, context and evidence
ETSI’s report on UCAAT 2026 describes AI quality as a central testing and standardisation challenge. The conference report highlights use-case-specific indicators, continuous evaluation, human insight, domain expertise, risk-based thinking and meaningful traceability alongside AI-driven testing and CI/CD. It also identifies realistic anonymisation, regulatory compliance and functional consistency as challenges for test data. These are conference observations, not controlled evidence that AI automation improves software quality.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
ETSI’s Rémi Caudwell, Chair of the UCAAT Programme Committee, characterized the shift this way: “AI is now seen as a productivity and quality accelerator for testers rather than a replacement, and automation has become an investment that must prove its value.” The statement reflects Caudwell’s view as reported by ETSI, not a measured industry-wide result. ETSI reported 140 participants at UCAAT 2026; that is event attendance, not a measure of adoption or consensus. Read ETSI’s UCAAT 2026 report.
What does AI mean for software testing?
AI adds testing questions; it does not remove the need for established software testing practice. ISO/IEC TS 42119-2 explains how the ISO/IEC/IEEE 29119 family applies to AI systems, including risk-based testing, test processes, test documentation and test approaches. The standard-family connection gives teams a way to build on familiar process and documentation while accounting for AI-specific risks. See the ISO preview for ISO/IEC TS 42119-2.
ETSI’s conference reporting suggests a practical focus for teams: define what quality means for the particular use case, evaluate continuously, bring domain expertise and human judgment into the process, and preserve traceable evidence. For test data, teams also need to consider whether anonymisation is realistic, regulatory requirements are met and data retains functional consistency. These are useful considerations, but the conference report does not quantify their effect or prescribe one universal implementation.
Rank #4
Which testing standards should practitioners know about?
| Development | Status and date | Scope | Practical implication |
|---|---|---|---|
| IEEE 3407-2025 | Active; published April 24, 2026, with ANSI approval on August 26, 2026, according to IEEE | Minimum requirements for end-to-end software testing automation tools and guidance for automated testing in software integration environments | A reference for requirements and processes for development, execution and maintenance; not an endorsement of a particular tool. |
| ISO/IEC/IEEE 29119-8 | Stage 60.00, “International Standard under publication,” on September 28, 2026, according to ISO | Requirements and guidance for model-based testing in the processes defined in 29119-2; assumes automated testware generation and execution | Useful for understanding the intended model-based testing framework. Tool selection and generation algorithm implementation are outside its scope. |
| ISO/IEC TS 42119-2 | The linked ISO preview describes the technical specification; no publication-status date is established here. | Application of the ISO/IEC/IEEE 29119 family to AI systems, including risk-based testing, process, documentation and approaches | Connects AI system testing to established testing processes while addressing AI-relevant testing approaches. |
What changed in testing certifications and professional development?
ISTQB’s 2026 news page lists several syllabus and credential announcements. These indicate additions to professional learning options; they do not establish career, salary or employer outcomes.
| Date in ISTQB news | Announcement |
|---|---|
| April 21, 2026 | CT-AI syllabus version 2.0 |
| April 27, 2026 | CT-GenAI minor update |
| May 6, 2026 | Advanced-Level Agile Tester launch |
| May 27, 2026 | Finance Testing and Quality in DevOps certification announcements |
For current details on these announcements, consult ISTQB’s 2026 news page.
Best Value
How should teams apply these developments?
- Separate status from scope. Treat IEEE 3407-2025 as active, but check ISO’s page for the publication status of 29119-8 before citing it as a published standard.
- Use standards for the question they address. IEEE 3407 concerns end-to-end automation tools; 29119-8 concerns model-based testing; ISO/IEC TS 42119-2 addresses applying the 29119 family to AI systems.
- Make AI quality measurable for the use case. ETSI’s UCAAT report points to use-case-specific indicators and continuous evaluation, alongside risk, human insight and traceability.
- Keep evidence and data practices in view. Consider documentation, traceability, realistic anonymisation, regulatory compliance and functional consistency when planning AI-related tests.
- Read certification announcements as learning options. The announcements establish syllabus or credential news, not a guaranteed professional result.
ScreenshotNeo for capturing test evidence
For teams that need website screenshots as test artifacts, ScreenshotNeo is a website screenshot API and MCP server for developers. It can return a screenshot or PDF from one GET request. Its clean-shot workflow can accept cookie or consent banners as a visitor and remove more than 60 known consent platforms, newsletter popups and chat widgets before capture; each step can be turned off. Bot checks or CAPTCHAs, blank pages, timeouts, failed loads and cache hits are not billed, and responses identify the page verdict and billing status in headers. AI agents can use its MCP server tools: take_screenshot, get_page_info and capture_pdf.
Or skip the browser setup
Use a single API request to save a screenshot. See the ScreenshotNeo API documentation for setup and parameters.
Quick Recap
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpCookie banners, popups and chat widgets are removed before the shot; bot checks, blank pages and failed loads are never billed. An MCP server lets AI agents take screenshots. The Free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000. Sign up free for 1,000 screenshots a month, with no card required.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
