Tokyo Test FestLalitkumar Bhamare · Beyond Automation · Tokyo Test Fest 2026
Tokyo Test Fest 2026 · Conference talk

Beyond Automation

How Agents Amplify (Not Replace) Testers with Agentic QCSD

Lalitkumar BhamareQE Thought Leader, EMEA · Accenture QESCreator of QCSD and Agentic QCSD
13 November 2026 · 15:25 to 15:55
Osaki Bright Core Hall, Tokyo
Photo: Takashi Miyazaki / Unsplash

About me

Before we begin
Lalitkumar Bhamare
Lalitkumar Bhamare
Sr. Manager, Accenture Song · Germany
EMEA Lead, Accenture QES Thought Leadership
More of my worktalesoftesting.com

Most organisations chase quality through process. I have spent my career proving it comes from consciousness: a deliberate, human-centred awareness woven into every stage of software delivery.

CEO, Chief Editor and Co-founder: Tea-time with Testers
Former VP Education and Board of Directors: Association for Software Testing, USA
Co-author: Global State of Testing Report
Contributing author: Taking Testing Seriously (Bach and Bolton)
Creator: QCSD and Agentic QCSD
Creator: QX (Quality Experience) framework
International keynote speaker: testing and quality coach
Advisory board member: German tech start-ups
EuroSTAR 2022 Best Paper Winner
EuroSTAR 2022Best Paper Winnerfor Quality Conscious Software Delivery
PractiTest 2025 Emerging QA Leader of the Year
PractiTest 2025Emerging QA Leader of the Year
01Section 01

The faster horse syndrome

Every generation of tools made testing faster. The cost of poor software quality kept rising.

Photo: Angelica Hasbon / Unsplash
The faster horse syndrome

Same rider, same road,
a faster horse

Every generation of tools changed how fast we test.
None of them changed what we test for, or the mindset behind it.

01 · What speed without quality costs
$2.41T

lost to poor software quality in the US in 2022, before counting $1.52T of technical debt

$5.4Bestimated Fortune 500 losses from a single faulty software update in July 2024
CISQ 2022 · Parametrix 2024
02 · What AI is accelerating
−7.2%

delivery stability where teams adopted AI

8×more duplicated code blocks in 2024, and 40% less refactoring
DORA 2024 · GitClear 2025
03 · Where testing spends its AI
70%

of AI use in testing goes to writing test cases

4.5%of teams are measured on business value. 56% are measured on coverage.
State of Testing 2026

We keep buying speed, and we keep paying for it in quality.

Photo: Catrin Ellis / Unsplash
02Section 02

Volume, Value, and Testing

What volume-driven testing costs, and what testing that creates value looks like.

Photo: Sasun Bughdaryan / Unsplash

How a volume-driven testing culture feeds the loop

Section 02 · Volume, Value, and Testing

Volume-driven testing is not neutral. It feeds itself, and every turn leaves quality a little worse.

Progress is measured by volumeTest cases, coverage, scripts
Testing starts after the buildNo time for questions before code
Defects are found lateWhen they cost the most to fix
Rework and firefightingThe sprint goes to fixing, not thinking
Upfront thinking is cut firstRisk analysis waits for a free afternoon
More pressure to show progressSo we count more tests
Degraded qualityEach turn adds more tests and less information
A reinforcing loop

Nothing in this loop asks whether the testing produced information anyone could act on. Every turn adds volume and removes time for thinking.

AI on the volume side

Point AI at writing more test cases, and the same loop simply turns faster.

What breaks the loop

Information that arrives while a decision is still cheap to change.

Upfront rigour before the build.

Not more tests after it.

What testing that creates value looks like

Section 02 · Volume, Value, and Testing

Most testing is measured on the tip. The value sits below the waterline.

What most teams countTest casesAutomated scriptsAcceptance criteria passed
What actually creates value
Shape what gets built
  • Risk assessment with the business
  • Quality criteria agreed for each release
  • Questioning requirements for gaps and contradictions
  • Testability asks before the design is fixed
  • Experience and accessibility reviews of designs
Widen what we look at
  • Product factors assessment for broad coverage
  • Deep, charter-based exploration
  • Performance, security and resilience risks
  • Test data that reflects real users
  • Experiments and what-if questions
Make the system easier to trust
  • Smart automation where it pays back
  • Logs, hooks and monitors asked for early
  • Contract and integration risks across teams
  • Risk-based quality gates with evidence
Learn and feed back
  • Learning from telemetry and error logs
  • Root cause analysis that changes how we work
  • Quality measures the business already tracks
  • Coaching developers and product owners on testing
  • Reporting risk in business language

Testing creates value when its information changes a decision while that decision is still cheap to change.

How the 70/30 problem makes value creation harder

Section 02 · Volume, Value, and Testing

Clerical and process burden takes the time that cognitive work needs. Testers feel it first, and the whole team pays for it.

70% · clerical and process work
30% · cognitive work
What fills the 70%
What gets squeezed into the 30%
Testers
Writing and maintaining test cases and scripts, status reports, triaging failing runs
Risk judgment, exploration, testability, test strategy
Developers
Rework on late defects, ticket and pipeline admin, handoffs
Designing for testability, thinking through edge cases, pairing on risk
Product owners
Backlog administration, status meetings, re-explaining requirements
Clarifying intent, agreeing quality criteria, deciding what not to build
Delivery leads
Reporting, coordination, chasing dependencies
Removing systemic risks, improving how the team works
The 70/30 problem

Clerical and process work crowds out the thinking, for every role.
Everything below the waterline has to fit into the 30%.

03Section 03

Quality Conscious Software Delivery

What QCSD is, how it runs and what it changed.

Photo: Jaipreet Singh / Unsplash

Introducing QCSD

Section 03 · Quality Conscious Software Delivery
Quality Conscious Software Delivery

Delivery of quality products by quality-conscious people using quality-empowering processes

using value-driven testing to facilitate it all.

Three notions of quality · QualiTri

Quality is never the property of the product alone

  • Products are built by people
  • People work in projects and follow processes
  • Project, people and product quality affect each other
QualiTri model by Lalit Bhamare
How it runs · the 4E cycle

Enable, Engage, Execute, Evaluate

The five phases

Section 03 · Quality Conscious Software Delivery

Every task, by every role, at every phase of the SDLC, done with more consciousness for quality.

Enable and engageExecuteEvaluate
Supporting activities
Testability improvement sessionsBi-weekly tester exchangePeriodic assessment of automation suitesLearning from production error logs

QCSD made upfront rigour work

Section 03 · Quality Conscious Software Delivery

Upfront rigour stopped being an ideal and became how the team worked. Lead time per release shows it.

In developmentBlockedIn QAMedian, before
18–49
Days lead time per release, before
11–13
Days lead time per release, after
Recognition and adoption
EuroSTAR 2022 Best Paper Award

QCSD was awarded the EuroSTAR Software Testing Best Paper award in 2022. Read the paper

Published industry case study

iFM engineering published its own case study of adopting QCSD.

Multiple Accenture clients

QCSD has been applied across several Accenture client deliveries.

The approach worked.Keeping it going, release after release, was the hard part.
04Section 04

The hidden challenges around upfront rigour

The underlying factors that kept steady upfront rigour out of reach, even when it clearly worked.

Photo: Luis Villasmil / Unsplash

Why upfront rigour stayed inconsistent

Section 04 · The hidden challenges around upfront rigour

Upfront rigour worked when it happened. These are the reasons it did not happen every time.

Clerical load

About 70% of a team’s capacity goes to clerical work. Upfront rigour gets what is left.

70%
30%
Cognitive overload

Seven product factors, every story, every sprint, held in people’s heads.

Fatigue

Depth depends on who is in the room and how tired they are. Sessions get shallower over time.

Fading motivation

Preparation is invisible effort. The clerical work is what gets counted and rewarded.

Delivery pressure

When a deadline moves, the thinking ahead is cut first.

The real question for AI in testing

Not a lack of ability or effort. A lack of capacity.
Can AI give testers that capacity back, and make them more effective with it?

05Section 05

Agentic QCSD: Amplify, not replace

Upfront rigour carried by AI agents, the judgment designed into them, and the people who still make the call.

Photo: Mick Haupt / Unsplash

Agentic QCSD: QCSD power-charged with AI agents

Section 05 · Agentic QCSD: Amplify, not replace

Same goal, same people, same processes. Upfront rigour made possible, affordable and more intelligent.

The sessions stay. A swarm of AI agents does the preparation for every story, and people keep the decision.

QCSD · since 2019The session, run by people
Agentic QCSD · todayCarried by an Agentic QE swarm or AI agent
Ideation
Requirements before ideation
testability scoringSkill
QX session
qe-qx-partnerAI agent
Impact mapping
human session · qe-qx-partner for evidenceHuman session
Refinement
Story analysis with SFDIPOT
qcsd-refinement-swarmSwarm
Product coverage session
qe-product-factors-assessorAI agent
Development
Developer testing for acceptance criteria
qe-test-architectAI agent
Code quality checks
qcsd-development-swarmSwarm
CI/CD
Automated quality gates
qcsd-cicd-swarm · qe-queen-coordinatorSwarm
Production
Production telemetry and error logs
qcsd-production-swarmSwarm
The 70/30 ratio, for the whole team

Cost, speed and quality together. The rigour that used to cost people-days now runs at the speed of the sprint, with every human gate still in place.

Without AI agents
70% clerical and process work
30% cognitive
With Agentic QCSD
70% clerical and process work30% clerical
30% cognitive70% cognitive work: risk, criteria, testability, exploration

Agentic QCSD: what lies beneath

Section 05 · Agentic QCSD: Amplify, not replace

People direct. Swarms of AI agents do the work. Agentic QE, the intelligence engine, learns from every sprint.

Human direction · validation is the control

5 human gates · GO, CONDITIONAL or NO-GO verdicts for every artefact · QualiTri dashboards for people, project and product

AI agent swarm layer · 8+2 swarms · 74+ AI agents · 75+ skills
Swarm orchestration · Queen coordinator
DesignDesign review swarm · QX
DiscoveryIdeation swarm
Test designRefinement swarm
Refine and buildDevelopment swarm
CI/CDCI/CD swarm
ProductionTelemetry · L3 loop
Cross-phase exchangeevery phase feeds every other · 13 DDD bounded contexts · PACTS principles
Write learnings
Read context · 2 ms
Intelligence engine · Agentic QE · every sprint smarter than the last
Knowledge graph memorySquad context and cross-phase memory
Fast indexAbout 2 ms reads; unchanged work is skipped
Learning pipelinePatterns reused across sprints and projects
Offline consolidationRun history distilled into reusable patterns
Self-tuning retrievalRetrieval and routing tune themselves
Self-review loopAI agents critique AI agents
Integration layer · 11+ platforms and systems · LLM-agnostic

GitLab · Jira · Confluence · SAP RFC · Kafka · Salesforce APIs · payment gateways · CI/CD · any approved model channel, with the organisation’s own keys

Cross-cutting rails
Cost-aware model routing5 routing tiers and a local booster · 70–85% lower token cost
Self-healing34+ known failure signatures · autonomous recovery
Quality gatesAnti-sycophancy scoring · hollow tests rejected · edge cases from learned history
Security and residencyFail-closed residency controls · sanitised environments · verified supply chain
Standards and ADRsCentral ADRs and readiness rules, a paved road for every squad

Applied at every layer, on every run, not bolted on afterwards.

Production learning re-primes planning, and the delivery lifecycle is only the first application: the same swarms, skills and governance assemble into many other solutions.

Amplify, not replace

Section 05 · Agentic QCSD: Amplify, not replace

The answer to that question: testers get capacity back, and AI agents make their judgment sharper.

The testerbrings the judgment
Critical thinking
Risk judgment
Testability assessment
Deep exploration
Business and domain context
Ethical judgment
Creative what-if questions
The final call
Amplifyreplace nothing
AI agentsbring the preparation
Preparation for every story
Breadth across all seven product factors
Evidence behind every verdict
Memory that carries across sprints
The same rigour at sprint six as at sprint one
Speed that frees people to think

QX AI agent review of a live customer journey

Demo 1 · QX AI agent · Design review · for the designer

A QX AI agent reviews a live customer journey. The designer decides. R replay

Discovery document review before Technical Discovery

Demo 2 · Business discovery · for the TPO

Eight AI agents review a discovery document. The TPO decides. R replay

Test strategy from requirements before development

Demo 3 · Test strategy · for testers and developers

One AI agent drafts the strategy and states its own limits. Testers decide. R replay

Many more ways to amplify testers, beyond automation

Section 05 · Agentic QCSD: Amplify, not replace

Agentic QCSD with the Agentic QE framework: AI agents for every kind of testing work, not just writing tests.

Test Generation7
Test ArchitectTDD SpecialistTDD RedTDD GreenTDD RefactorProperty TesterTest Idea Rewriter
Test Execution4
Parallel ExecutorFlaky Test HunterRetry HandlerIntegration Tester
Coverage Analysis3
Coverage SpecialistGap DetectorMutation Tester
Quality Assessment9
Queen CoordinatorFleet CommanderQX PartnerQuality GateCode ReviewerDeployment AdvisorIntegration ArchitectRisk AssessorDevil’s Advocate
Defect Intelligence4
Defect PredictorPattern LearnerRoot Cause AnalyzerRegression Analyzer
Learning Optimization3
Learning CoordinatorTransfer SpecialistMetrics Optimizer
Security Compliance4
Security ScannerSecurity AuditorSecurity ReviewerPentest Validator
Chaos Resilience4
Chaos EngineerLoad TesterPerformance TesterPerformance Reviewer
Code Intelligence5
Code IntelligenceKnowledge Graph BuilderCode Complexity AnalyzerDependency MapperImpact Analyzer
Contract Testing3
Contract ValidatorGraphQL TesterIntegration Reviewer
Requirements Validation4
Requirements ValidatorBDD GeneratorProduct Factors AssessorQuality Criteria Recommender
Visual Accessibility3
Visual TesterResponsive TesterAccessibility Auditor
Enterprise Integration7
SOAP TesterSAP RFC TesterSAP IDoc TesterMiddleware ValidatorOData Contract TesterMessage Broker TesterSOD Analyzer
n8n Workflow Testing14
Workflow ExecutorUnit TesterIntegration TesterTrigger TesterExpression ValidatorNode ValidatorBDD Scenario TesterChaos TesterPerformance TesterSecurity AuditorCompliance ValidatorMonitoring ValidatorCI OrchestratorVersion Comparator
74+ AI agents · 14 domains

Queen-led hierarchical coordination · work stealing for 3 to 5 times throughput · PACTS principles throughout · including the 14-AI-agent n8n workflow-testing swarm

The takeaway

Testing has always been an information business

AI agents can bring more of that information to the surface, and help testers communicate it so it changes decisions. If we use them right.

01
FromAI that writes more tests
ToAI agents that surface what no one had time to find

Risks, gaps and contradictions across all seven product factors, for every story, before the build.

02
FromReports nobody acts on
ToEvidence that changes decisions while they are cheap

Every verdict carries its reasons, told in the language of the business.

03
FromTrusting what the AI produced
ToTesters who question it and make the call

Judgment, context and ethics stay with people. AI agents make them sharper.

Used right, AI makes testers more significant than ever.

Amplify the thinking.

Not the volume.

Dedication

For Keizo Tatsumi

A lifelong tester and my friend of ten years. He is one of the reasons I am in Tokyo today.

  • 1976Joined Fujitsu’s software inspection department, later led its Software QA Division
  • 1987Co-authored “Conceptual support for test case design” at COMPSAC, early work on combinatorial testing
  • TodayJapan’s software testing historian, NPO ASTER member, and lead of the Japanese translation of the State of Testing report

Thank you, Tatsumi-san.本当にありがとうございました。

Keizo Tatsumi and Lalitkumar Bhamare in Tokyo
Tatsumi-san and me · Tokyo, November 2026

The faster horse won’t save us.

A thinking team, amplified, will.

Lalitkumar Bhamarelinkedin.com/in/lalitbhamare · teatimewithtesters.com · talesoftesting.com
Get Agentic QCSDOpen source, MIT licensed, built on the Agentic QE framework
Photo: Mathew Schwartz / Unsplash
Lalitkumar Bhamare·Tokyo Test Fest 2026·Accenture