/QAble Weekly/Vol. 017 · 16 Oct 2026

● This week’s signal » Testing is getting measurably faster. Almost none of the numbers proving it say anything about whether defects are found.

Weekly

Signal Over Noise

‹ PrevNext ›

For Engineering
Leaders

5-minute read

‹ PrevNext ›

Friday, 16 October 2026 · Vol. 017

In Brief

ANZ weighs handing software testing to a single partnerOct 12
Cloudflare acquires Deno, maker of the JavaScript runtimeOct 9
Character.AI files for Chapter 11 bankruptcyOct 12
BrowserStack makes real-browser load testing generally availableOct 14
Google releases Gemini 4 Argon publiclyOct 13
79% say AI writes code faster while the release cycle is unchangedOct 7
Arena raises $200M at a $3.1B valuation to evaluate models and agentsOct 8
Pluto Security exits stealth with $42M raised in totalOct 13
ANZ weighs handing software testing to a single partnerOct 12
Cloudflare acquires Deno, maker of the JavaScript runtimeOct 9
Character.AI files for Chapter 11 bankruptcyOct 12
BrowserStack makes real-browser load testing generally availableOct 14
Google releases Gemini 4 Argon publiclyOct 13
79% say AI writes code faster while the release cycle is unchangedOct 7
Arena raises $200M at a $3.1B valuation to evaluate models and agentsOct 8
Pluto Security exits stealth with $42M raised in totalOct 13

Story of the Week

ANZ is restructuring QA on numbers that measure speed, not quality

On 12 October, QA Financial reported that ANZ is considering consolidating its software testing under a single strategic partner, as part of a proposed technology restructure affecting more than 400 roles, with over 100 permanent jobs potentially going in New Zealand. The Australian Financial Review reported the bank had been in discussions with Infosys and HCLTech, though negotiations were not finalised. ANZ has confirmed it is considering changes to its technology organisation, saying it is “bringing together related functions like data, AI and engineering”, but it has not confirmed the job numbers or appointed a testing provider. Here is the part worth sitting with. ANZ has spent years building AI-assisted QA, through an in-house platform called Ensayo AI, built with HCLTech and Amazon Web Services. In a 2024 account, the bank reported a 72% cut in API testing time and a 56% cut in integration testing time. Its platform engineering lead said they were “surprised to find out our API testing time has been dramatically cut by 72 percent”. Those are real gains and they are worth having. But read what they measure. Both are elapsed time. Neither says anything about defect detection or production reliability, a gap QA Financial noted explicitly. A testing function can get dramatically faster while catching no more than it did before, and these are the figures that make the efficiency case for restructuring the people who do it.

Why it matters: The business case for reducing a quality function is being built on throughput metrics, because throughput is what the tooling reports. HCLTech co-built the AI testing platform whose results form part of the efficiency picture, and is among the firms discussed for the testing contract. No published ANZ figure shows what happened to escaped defects or production incidents, which is the only measure that answers whether testing improved.

ANZ has confirmed it is considering changes to its technology organisation. It has not confirmed the reported job numbers or any testing provider. · ANZ, via QA Financial

WeeklySection 01 · This Week’s Launches

Launch

BrowserStack ships load testing built on the premise that passing load tests lie

What: BrowserStack shipped load testing that drives real browsers, on the argument that server-side load tests pass while customers cannot check out. Elsewhere, Cloudflare bought Deno and put an end date on a runtime many teams ship with.

On 14 October, BrowserStack made Load Testing generally available, running real browser sessions and API traffic in a single test, at up to 1 million API virtual users and 1,000 browser virtual users per test across geographies. The pitch is not the scale. It is the diagnosis. Traditional load tests measure server response times, so a site can pass comfortably while the browser side of the page falls over, which is what the customer actually experiences. Chief executive Ritesh Arora framed the failure mode in six words that belong on a wall: “the test said the servers were fine.” The timing is seasonal, aimed at teams checking their systems before peak shopping days, when a checkout page that will not load is measured directly in lost revenue. Strip away the product and the argument underneath is this week’s theme stated by a vendor with something to sell: a green test result is only as meaningful as the relationship between what it measures and what your users do.

Why it matters: A passing test that measures the wrong layer is more dangerous than no test, because it produces confidence rather than uncertainty. Server response time was always a proxy for user experience, and proxies drift from the thing they stand in for. Ask of every green suite you own: what would this still report as healthy while customers were unable to complete a purchase?

Launch Log

BrowserStack Load Testing
Generally available on 14 October, combining real browser sessions with API traffic in one test, up to 1 million API virtual users and 1,000 browser virtual users.
Gemini 4 Argon
Google’s flagship released publicly on 13 October at $2 and $10 per million tokens, introductory rates it plans to double after 30 November.
Pluto Security
Out of stealth on 13 October, monitoring the AI tools employees use and the applications they build themselves, including vibe-coded software.

WeeklySection 02 · Frameworks & Failures

Frameworks

Four questions that separate a faster test suite from a better one

Every number in this edition is real, and almost none of them measure quality. ANZ’s 72% is elapsed time. A green load test is server response time. “Significantly faster code generation” is keystrokes. These are legitimate measurements of legitimate things, and every one of them can improve while your software gets worse. So before a testing metric is used to justify a decision, put it through four questions. First, does it measure time or outcome? Faster, cheaper and more are throughput. Escaped defects, incident rate and time to correct diagnosis are outcomes. Only the second group can tell you whether testing is working. Second, could this number improve while quality degrades? If it could, it is a supporting metric and must never travel alone. Third, who produced it? ANZ’s testing figures came from the platform being evaluated. That is not dishonesty, it is the ordinary situation, and it means the number needs an independent counterpart. Fourth, what does it measure that your user never experiences? That gap is where the test said the servers were fine. Against this week’s most consequential decision, the exercise is uncomfortable: a bank is weighing the future of more than 400 technology roles, and the published evidence covers speed, not defects found.

Why it matters: Pair every throughput metric with an outcome metric, and never present one without the other. Treat any quality figure produced by the system under evaluation as a hypothesis that needs independent corroboration. If you cannot state what your test suite would miss, you do not yet know what it is worth.

Research

Generating code got faster. Shipping it did not.

A survey of 300 senior engineering leaders working on mission-critical software, conducted by Coleman Parkes for Undo and reported on 7 October, puts numbers on where the time actually goes. Teams spend an average of 9.8 hours a week producing code and 16.9 hours a week debugging it, roughly 42% of the working week. And 79% said AI agents generate code significantly faster, while the release cycle is no faster than before. That sentence is the whole argument. The constraint moved rather than disappeared. Three findings show where it moved to: 35% of generated code reaches production before the team has fully understood it, 93% have had a root cause diagnosed incorrectly because of hallucination, and 81% had at least one production incident in six months. Undo’s chief executive Greg Law put the asymmetry plainly: “while agents are great at writing reams of code quickly, they’re less capable at debugging it.” Note that the sample is weighted toward complex C and C++ codebases, so it describes the hard end of the industry rather than its average.

Failures & Incidents

ANZ weighs consolidating testing under one partner (Oct 12)
A proposed technology restructure affecting more than 400 roles, with discussions reported with Infosys and HCLTech. ANZ has confirmed it is considering changes but not the job numbers or any provider.
QA Financial
81% had a production incident in the last six months
And 93% have had a root cause diagnosed incorrectly because of hallucination, among 300 leaders working on mission-critical software.
Coleman Parkes for Undo, Oct 7
Microsoft 365 Global Secure Access degraded for about 11 hours (Oct 13)
Users routing Outlook, Teams, OneDrive and Cloud PCs through GSA were affected, attributed to infrastructure performing below acceptable thresholds. Reported by a third-party tracker rather than a vendor postmortem.
IncidentHub

The Wider Beat

Cloudflare bought Deno, and a runtime thousands of teams depend on now has an end date

On 9 October, Cloudflare acquired Deno, the company behind the JavaScript and TypeScript runtime built by Ryan Dahl, who also created Node.js. Terms were not disclosed. Deno had raised about $26M, including a $21M Series A led by Sequoia in 2022. The whole team is joining, and Dahl will lead work on making Cloudflare’s Workers model self-hostable. What the acquisition is actually for is a Rust binary called celld, shipped quietly in August, which lets teams run the Workers programming model on their own servers instead of only on Cloudflare’s network. That code is being merged into the open-source workerd runtime. Now the part that belongs in your risk register rather than your newsletter. Deno’s core team stops developing the runtime in 2027, after one final year of maintenance and security updates, and Deno Deploy shuts down around April 2027, with paying customers helped onto Workers. This is not a failure, and the open-source project does not vanish. But if Deno is in your stack, an external commercial decision just converted a live dependency into one with a published expiry date, and it did so in a single announcement you did not get a vote on.

WeeklySection 03 · Editor’s Note

By the Numbers · The AI quality gap, quantified

QAble Weekly analysis · sources per figure

72%

cut in ANZ’s API testing time after its AI testing platform, a figure that measures elapsed time rather than defects found

Source: ANZ, 2024 account, via QA Financial, Oct 12

79%

of engineering leaders say AI generates code significantly faster, while the release cycle is no faster than before

Source: Coleman Parkes for Undo, n=300, via InfoQ, Oct 7

16.9 hrs

spent debugging per week, against 9.8 hours writing code, about 42% of the working week

Source: Coleman Parkes for Undo, via InfoQ, Oct 7

35%

of generated code reaches production before the team has fully understood it

Source: Coleman Parkes for Undo, via InfoQ, Oct 7

Editor’s Note

Viral Patel, Co-Founder of QAble — Viral PatelCo-Founder, QAble

“A bank is weighing the future of more than 400 technology roles, partly on the strength of figures showing its testing got 72% faster. No published figure shows whether it got better.”

If your testing got faster and worse at the same time, which number on your dashboard would move?

I want to be fair to ANZ here, because the numbers are real and the gains are worth having. Cutting API testing time by 72% and integration testing by 56% is genuine engineering work, and I would be pleased with it.

But look at what both figures measure. Elapsed time. How long the testing took. Neither of them tells you whether more defects were caught, whether fewer incidents reached customers, or whether anything about the software got better. A test suite can run twice as fast and catch exactly as much as it did before. It can run twice as fast and catch less.

This is not a criticism of one bank. It is the ordinary situation almost everywhere, including, I suspect, in your dashboards and mine. Our tooling reports duration, pass rates and coverage, because those are cheap to count. Escaped defects and incident rates are harder, slower and less flattering, so they show up less often in the deck that justifies a decision.

The week supplied its own illustration. BrowserStack shipped a product whose entire argument is that load tests pass while customers cannot check out, and its chief executive summed up the failure in six words: the test said the servers were fine. Meanwhile a survey of 300 engineering leaders found 79% saying AI generates code significantly faster while their release cycle is no faster at all. Faster at the part we measure. Unchanged at the part that matters.

None of this means the metrics are useless. It means they are incomplete, and that incompleteness becomes dangerous at exactly the moment someone uses them to decide who still has a job.

So before your next quality number goes into a slide, ask what it would look like if your testing got faster and worse at the same time. If the answer is that it would look identical, you are not measuring quality. You are measuring speed and hoping.

WeeklySection 04 · Briefing

Funding & M&A

Arena $200M · Series B
Pluto Security $42M · Seed and Series A
Meticulous $15M · Series A

Research

Coleman Parkes for Undo, AI agents in complex codebases
Among 300 leaders on mission-critical software: 9.8 hours a week writing code against 16.9 debugging, 79% report faster generation with no faster releases, and 35% of generated code reaches production before anyone has fully understood it.
Arena Alignment Index
Compares 27 models across 90,000 real-world agent sessions, an attempt to measure agent behaviour in situ rather than on static benchmarks.

Quote of the Week

“Code generation is relatively inexpensive, but that means code review and the feedback loop become the bottleneck.”

Zach Davis, Director of Engineering, LaunchDarkly

Market Signals

01Testing efficiency is being reported in elapsed time, and elapsed time can improve while defect detection stays flat or falls.
02Quality functions are being restructured against throughput figures, because throughput is what the tooling measures and reports.
03Faster code generation is not producing faster delivery, which means the constraint has moved downstream rather than disappeared.
04Evaluation, pre-merge testing and runtime monitoring were each funded separately in the same eight days.
05Dependency risk is now set by acquisition as much as by code, as Cloudflare’s purchase of Deno and its 2027 sunset showed this week.
06A green test result is only as meaningful as the distance between what it measures and what the customer actually does.

Community & Debate

What does a 72% faster test suite actually buy you?

The ANZ figures prompted an uncomfortable round of checking as teams realised their own dashboards report speed and say nothing about escaped defects.

Hacker News

Nine hours writing, seventeen hours debugging

The Undo numbers landed because they matched what people already suspected about where their week goes, and gave them a figure to cite.

Reddit r/ExperiencedDevs

The test said the servers were fine

BrowserStack’s framing travelled further than its product, as teams swapped stories of green dashboards during customer-visible outages.

Ministry of Testing

Elsewhere in Tech

Character.AI files for Chapter 11

Disney is the stalking-horse bidder at $20M, but only for a non-exclusive perpetual licence to certain IP and claims, not the company. Assets and liabilities are put at $50M to $100M. The platform runs during proceedings and winds down if no operating buyer appears.

Delaware bankruptcy court, Oct 12

IonQ to buy Elisity for up to $1.3B

An all-stock deal, including up to $150M of earnout, pairing post-quantum cryptography with Elisity’s zero-trust platform. IonQ shares fell on the news. Expected to close in Q4, subject to regulatory approval.

IonQ 8-K, Oct 12

ASML posts €11.7B in quarterly net sales

Net income of €5.0B and 121 lithography systems sold, against 91 the previous quarter. Q4 guidance is €14.2B to €15.2B, with full-year sales expected at €44B to €45B.

ASML Q3 results, Oct 14

Apple launches a $299 smart home hub

HomeView ships on 13 November with a 7-inch display and an A18 chip, recognising up to six household members by face. It will not be sold in the EU. The refreshed HomePod mini 2 is $149, from 30 October.

Apple, Oct 13

DOJ details a North Korean laptop farm crackdown

Searches at more than 40 Texas residences in late September seized roughly 187 laptops and devices. Prosecutors say facilitators helped North Korean workers earn over $3M from about 70 US companies across 17 states.

US Attorney, N.D. Texas, Oct 13

Sources: 01 ANZ Bank weighs testing outsourcing as AI reshapes QA (QA Financial, Oct 12) | 02 ANZ restructuring 400 roles via offshoring, redundancies (HR Leader, Oct) | 03 BrowserStack launches real-browser load testing ahead of holiday sales (ANI, via The Tribune, Oct 14) | 04 Survey finds AI-generated code increases debugging and failure rates and creates a comprehension gap (InfoQ, Oct 7) | 05 Arena raises $200M Series B at a $3.1B valuation (Arena, Oct 8) | 06 Meticulous raises $15 million Series A led by Chemistry (Pulse 2, Oct 9) | 07 Pluto Security raises $42M to secure the AI tools employees build themselves (Crypto Briefing, Oct 13) | 08 Google releases Gemini 4 Argon AI model to public (American Bazaar, Oct 14) | 09 Cloudflare acquires Deno to improve its Workers programming model (TechCrunch, Oct 10) | 10 Disney offers $20M for Character.AI assets as startup files for Chapter 11 (Deadline, Oct 12) | 11 IonQ to acquire Elisity, definitive agreement announcement (IonQ 8-K, Oct 12) | 12 ASML third-quarter 2026 financial results (ASML 6-K, Oct 14) | 13 Apple makes another push into the smart home market with HomeView (TechCrunch, Oct 13) | 14 DOJ raids Texas laptop farms in North Korean IT worker crackdown (The Record, Oct 13)