Tokyo Test FestAgentic QCSD · Tokyo Test Fest 2026
02Section 0213:20

The diagnosis

Record AI adoption, the same old metrics, and where a tester’s time goes.

State of Testing 2026 · The 70% problem

Photo: Homa Appliances / Unsplash

Record AI adoption, same old metrics

Chapter 00 · The diagnosis

State of Testing Report 2026, by PractiTest and Tea-time with Testers.PractiTestTea-time with Testers

76.8%
of teams use AI in testing
70%
of that AI usage goes to test case creation
4.5%
are measured on NPS or business value

The industry upgraded its tools but not its thinking. We are still in the test factory, measured on pass and fail, rewarded for volume rather than value.

Source: State of Testing 2026. 56% of teams are measured on test coverage.

The 70% problem · where a tester’s time goes
70% clerical
30% expert

Clerical burden

  • Documentation and artefact management
  • Repetitive analysis and reporting
  • Automation maintenance
  • Status updates and test reporting
  • Gathering insights from failing tests

Expert work

  • Critical thinking and risk judgment
  • Testability assessment
  • Deep exploration
  • Context analysis
  • Strategic testing

The 70/30 split is Lalit’s own observation across teams, not a published figure.

03Section 03

Quality Conscious Software Delivery

Where QCSD came from, what it is, what it changed, and what it costs to run by hand.

Origin · What QCSD is · Five phases · Outcome · Cost of rigour

Photo: Jaipreet Singh / Unsplash

Where QCSD came from

Chapter 01 · Born out of necessity

A real delivery team, a real product, and a backlog that kept growing faster than the team could ship.

The delivery team
A passionate team that was determined to make things better

What the team was living with

Why projects stay stuck · Jerry Weinberg's feedback effect
Value of quality unclearNobody can say what quality is worth
Engineering actions not aligned with business goalsWork is busy, not valuable
No motivation to achieve qualityQuality loses every trade-off
No know-how to achieve itNobody learns how to build it in
No motivation to measure itSo its value stays unclear
System collapseEach turn of the loop makes the next one worse

What QCSD is

Chapter 02 · Quality Conscious Software Delivery
The goal

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

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

Engineering actions aligned with business goals · impact mapping

Every build, feature, release and issue weighed against one business question

Why

Increase test automation by 80%

Who

Feature testers · API testers · central automation team · operations

How

Automate build-qualifier scenarios · support CI pipelines

What

Scenario lists · executable scripts · smoke-test pipeline · CI dashboard

The five phases

Chapter 03 · The framework

Quality work placed at every phase of delivery, with a named session for each. Select a phase.

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

The outcome

Chapter 04 · Results, recognition, adoption
In developmentBlockedIn QAMedian, before
18–49
Days lead time per release, before
11–13
Days lead time per release, after
  • Reduced lead time
  • No obvious bugs
  • Nominal production bugs
  • Less rework
  • More features released per sprint
  • More tickets pulled within the sprint
  • Continuous discovery
  • Continuous feedback
  • Continuous quality
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 cost of upfront rigour

Chapter 05 · Why not every team can do it

QCSD works because it is always cheaper to do things right the first time. Doing them right the first time means putting skilled people in a room before a line of code exists. Add the sessions one feature needs.

A team working through sessions together
People in the room for one feature
0sessions
0people seats
Everyepic and every sprint
  • Senior people's time, repeated for every feature
  • The first thing cut when a deadline moves
  • Depends on a coach in the room to run it well

The cost, speed and quality trade-off

Chapter 05 · Why not every team can do it
The trade-off delivery teams have lived with for 30 years

Cost, speed, quality: pick two

Upfront rigour has always pulled quality up at the price of cost or speed.

Select two corners.
Quality Speed Cost
04Section 04

Agentic QCSD and Designed Agency

Upfront rigour carried by AI agents, and the judgment designed into them.

Agentic QCSD · From session to swarm · The 70/30 split · Symptoms answered · Designed Agency

Photo: Mick Haupt / Unsplash

Agentic QCSD: QCSD power-charged with AI agents

Chapter 06 · Upfront rigour, carried by AI agents

Same goal, same people, same processes. AI agents make the upfront rigour possible, affordable and more intelligent.

Delivery of qualityProducts
by quality-consciousPeople
using quality-empoweringProcesses
power-charged withAI agents
= Agentic Quality Conscious Software Delivery

Every QCSD session now has a swarm of AI agents that does the legwork for every story, in every sprint. People keep the decisions.

Possible

The rigour runs on every epic and every story, without waiting for a coach or a free afternoon.

Affordable

AI agents gather, analyse and draft; people spend their time only at the gates that need judgement.

More intelligent

One shared knowledge graph learns from every swarm, every squad and every production incident.

The blind men and the elephant
Why one shared knowledge graph

Every knowledge worker holds one true part

  • The PO, the architect, the developer and the tester each know a different part of the truth
  • Agentic QCSD assembles those parts in one shared memory that every swarm reads
  • Each decision is made with the combined truth on the table

From QCSD session to Agentic QE swarm

Chapter 06 · Agentic QCSD

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
This afternoon
Ideation
Requirements before ideation
qe-requirements-validator
Risk storming
qcsd-ideation-swarm
Exercise 1
Quality criteria session
qe-quality-criteria-recommender
Exercise 1
Testability session
testability scoring
Exercise 1
QX session
qe-qx-partner
Impact mapping
human session · qe-qx-partner for evidence
Refinement
Story analysis with SFDIPOT
qcsd-refinement-swarm
Product coverage session
qe-product-factors-assessor
Exercise 2
Development
Developer testing for acceptance criteria
qe-test-architect
Exercise 3
Code quality checks
qcsd-development-swarm
CI/CD
Automated quality gates
qcsd-cicd-swarm · qe-queen-coordinator
Exercise 4
Production
Production telemetry and error logs
qcsd-production-swarm
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.

How Agentic QCSD changes the 70/30 split

Chapter 06 · Agentic QCSD

The clerical 70% moves to AI agents. The expert 30% becomes the tester’s work at every gate.

70% clerical · now prepared by AI agents
30% expert · the tester’s work
Prepared by AI agents for every story
  • Documentation and artefacts→Phase reports drafted for every story
  • Repetitive analysis→SFDIPOT and risk scoring on every story
  • Automation maintenance→Tests generated from the test ideas
  • Status updates and reporting→GO, CONDITIONAL or NO-GO verdicts with evidence
  • Insights from failing tests→Root cause analysis and defect prediction
Where testers now spend their time
  • Risk judgmentDecide which risks block the story
  • Critical thinkingChallenge the verdict and its evidence
  • TestabilityAsk for the change that makes it testable
  • Deep explorationExplore where the AI agents did not look
  • ContextBring the business and domain knowledge
Nothing is decided for you. AI agents prepare the evidence; every gate still has a person who makes the call.

Symptoms and the methods that answer them

Chapter 07 · Built by design
Built by design to break the loop. Every symptom the team lived with has a named QCSD method, tried and tested in delivery since 2019, and each method is now carried by an Agentic QE swarm or AI agent.

Select a symptom.

Agentic QCSD is built on Designed Agency

Chapter 08 · Designed Agency

The industry adopted the word agentic faster than it examined what the word means. Designed Agency compels us to think about and define what it means in our context.

Why most AI agents are called agentic
  • An LLM decides the next step
  • It calls tools
  • It runs in a loop
What that leaves out
  • Encoding judgment without architecture is just a prompt
  • Architecture without encoded judgment is just plumbing
  • Without honest approximation there is no way of knowing whether what was built is any good
Designed Agency

Judgment deliberately designed in by practitioners who know the work deeply enough to encode it, architect it and measure it honestly.

  • Encoded the threads, the material the cloth is made of
  • Structured the loom, the instrument that acts on the material
  • Approximated the contact between threads that gives the cloth its texture
The cloth needs all three together. Agentic QCSD and the Agentic QE framework are built on all three.

The three dimensions of Designed Agency

Chapter 08 · Designed Agency

The three dimensions and how they show up in the AI agents. Select a dimension.

Designed AgencyJudgment deliberately designed in

Further reading: Congratulations on your agent. Does it have agency? · Lalitkumar Bhamare on LinkedIn

Tokyo Test Fest 2026 · Half-day tutorial

The 70% Problem

Reclaiming Testing’s Intellectual Core with Agentic QCSD

Lalitkumar BhamareDragan Spiridonov
12 November 2026 · 13:00–16:00
Cybozu, Nihonbashi, Tokyo
bit.ly/ttf-agentic-qcsd
Photo: Ramon Buçard / Unsplash
01Section 0113:00–13:20

Before we start

Your hosts, the run of show, your workspace and a warm-up exercise.

Your hosts · Run of show · Setup · Exercise 0

Photo: Marvin Meyer / Unsplash

Who is running this room

Your hosts

Lalitkumar Bhamare

EMEA Lead, Quality Engineering Thought Leadership · Accenture Song

  • Creator of QCSD, Quality Conscious Software Delivery. EuroSTAR 2022 Best Paper.
  • Creator of Agentic QCSD. Key contributor to the open-source Agentic QE framework.
  • Co-Founder and Chief Editor, Tea-time with Testers. Former VP Education, AST.
  • Co-author, State of Testing 2026. Emerging QA Leader of the Year 2025.

Dragan Spiridonov

Head of Agentic Quality Engineering · Cognitum One · joining by video today

  • Creator of the Agentic QE framework. Evolved PACT into PACTS.
  • 29 years in technology, 12 of them building quality engineering functions in enterprises.
  • Creator of the Agentic QE Fleet. Founding member, Serbian Agentic Foundation Chapter.
  • Former programme chair, Belgrade Test Conference. Writes at forge-quality.dev.

Run of show

13:00–16:00
Part one · 13:00 to 14:35
13:00Welcome, hosts, setup check10 min
13:10Exercise 0 · Warm-up, the knowledge graph10 min
13:20The diagnosis and the story of Agentic QCSD15 min
13:35Architecture, then AQE intro by Dragan on video20 min
13:55Exercise 1 · Ideation swarm on the epic25 min
14:20Coffee break15 min
Part two · 14:35 to 16:00
14:35Exercise 2 · Refinement, product factors15 min
14:50Exercise 3 · Development, tests20 min
15:10Exercise 4 · CI/CD, gate and decide15 min
15:25Exercise 5 · Self-learning10 min
15:35Apply PACTS and your adoption roadmap20 min
15:55Wrap-up and Q&A5 min
Stretch: Exercises 2b and 2c, for early finishers and after the session.

Setup in your workshop workspace

13:00–13:10

Codespaces runs on GitHub. DevPod runs locally through Docker. AI agent exercises use your own model access and tokens. Workshop repo: bit.ly/ttf-agentic-qcsd

Container · Codespaces or DevPod + Docker
  1. devpod up . --provider dockeror open the repo in a Codespace
  2. bash .devcontainer/prepare-workshop.sh
  3. bash .devcontainer/verify.shthen npm run test:run
  4. Sign in to your AI agent inside the container.Trust the workspace, approve the AQE MCP server.
  5. Open LAB.md.Exercise 0 is already prepared: inspect its output.
Manual · on your laptop
  1. git clone https://github.com/fndlalit/TTF-Agentic-QCSD-Workshop
  2. npm install -g agentic-qe@latestaqe init --auto
  3. npm install
  4. aqe code index src/
  5. npm install -g @huggingface/transformers@4.2.0
  6. aqe learning import -i seed/aqe-seed-patterns.json
Requirement

Node 22.13 or newer and npm 10+.

Manual setup

Clone near your home folder. Deep paths lose files from the graph.

Not on Claude Code?

Add --with-copilot, --with-cursor or --with-kiro.

Full guide: docs/DEVCONTAINER.md and README.md in the tutorial repo.

Warm-up: give the fleet a map of your code

Exercise 0 · 13:10–13:20

About 2 minutes · in your terminal, not through your AI agent · no API key, no tokens

1 · Index
Terminal
aqe code index src/

21 files · 102 nodes · 117 edges

2 · Verify
Terminal
aqe hg stats

Manual setup: 140 nodes · 102 edges.
Container: 110 nodes · 89 edges.

3 · Baseline
Terminal
aqe memory usage

21 entries · 81 vectors, before you begin

Static analysis and local embeddings inside your workspace. No provider key, no tokens. In the container, prepare-workshop.sh has already run these three commands.

05Section 0513:35–13:55

The engine

Swarm architecture, feedback loops, and the Agentic QE framework from its creator.

Architecture · The engine · AQE intro by Dragan

Photo: James Wainscoat / Unsplash

Swarm architecture and feedback loops

Architecture · 13:35–13:40

Five swarms, one per phase, each handing its findings forward. Four feedback loops carry what each phase learned back to the phase that can act on it.

Ideation9 AI agents · 4 skills
›
Refinement10 AI agents · 3 skills
›
Development10 AI agents · 4 skills
›
CI/CD10 AI agents · 4 skills
›
Production12 AI agents · 5 skills
Four feedback loops: strategic, tactical, operational, quality criteria

The engine that powers it all

Architecture
Queen coordinator, model router, reasoning bank, dream cycles, fleet commander, strange loop

The Agentic QE framework, from its creator

AQE intro · Dragan Spiridonov · video · 14 min
Dragan Spiridonov · Head of Agentic Quality Engineering, Cognitum One · creator of the Agentic QE framework · github.com/proffesor-for-testing/agentic-qe
06Section 0613:55–15:35

Hands-on lab

Five exercises on one checkout app, from the epic to the release call.

Ideation · Refinement · Development · CI/CD · Self-learning

Photo: Rahul Mishra / Unsplash

Ideation: surface risk before any code

Exercise 1 · Ideation · 13:55–14:20

About 20 minutes · qcsd-ideation-swarm · installed as a skill, not a command file

Prompt · paste into your AI agent
/qcsd-ideation-swarm

Analyze the guest-checkout epic in requirements/epic-checkout.md, using requirements/user-stories.md and requirements/acceptance-criteria.md for context. Work from these files only, with no web research. Skip the security audit: Exercise 4 covers security.
Save all reports under reports/01-ideation-swarm/.
Save learnings and persist patterns.
Save toreports/01-ideation-swarm/Two versions in LAB.md
While it runs

Read the epic yourself. Which verdict would you give: GO, CONDITIONAL or NO-GO?

Before you start

Your AI agent is signed in inside this workspace and the AQE MCP server is approved. Not on Claude Code? LAB.md has a step list.

Exercise 1 debrief

Last 5 minutes of the slot · in pairs, then the room

Ideation: surface risk before any code

1In the report

Which verdict did you get?

NO-GO, CONDITIONAL or GO. Find it and its top blockers in the executive summary.

2In pairs

Which contradiction between the epic, the stories and the criteria did it find?

Check one against the files in requirements/. Is it real?

3In the room

What would you refuse to start building without?

Show of hands on the verdict, then one blocker per table.

Open reports/01-ideation-swarm/

Our measured run (open after the debrief)

Measured on 6 November 2026, agentic-qe 3.15.18, Claude Code, unattended: 6.7 minutes, $2.25. Interactive runs take longer because you approve tool calls. Verdict in this run: CONDITIONAL, 39 risks (4 critical), testability 59%, requirements completeness 46%. The skill’s stricter threshold table would read NO-GO, and the report says so.

14:20–14:35

Coffee break

Back at 14:35. Keep the report from Exercise 1 open.

Next · Exercise 2 · Refinement: product factors before coverage

Photo: Karl Fredrickson / Unsplash

Refinement: product factors before coverage

Exercise 2 · Refinement · 14:35–14:50

About 10 minutes · qe-product-factors-assessor

Prompt · paste into your AI agent
Use qe-product-factors-assessor to analyse the guest-checkout product from requirements/epic-checkout.md and requirements/user-stories.md. Produce a product-factors (SFDIPOT) assessment and save it to reports/02-refinement-product-factors.md.
Save learnings and persist patterns.
Save toreports/02-refinement-product-factors.mdTwo versions in LAB.md
While it runs

Which of the seven factors do you expect to carry the most risk here?

The seven factors

Structure, Function, Data, Interfaces, Platform, Operations, Time.

Exercise 2 debrief

Last 5 minutes of the slot · in pairs, then the room

Refinement: product factors before coverage

1In the report

Which of the seven factors got the most test ideas, and which the fewest?

Structure, Function, Data, Interfaces, Platform, Operations, Time.

2In pairs

Which test idea would you not have thought of yourself?

Then find one that is generic enough to fit any checkout.

3In the room

Which factor carries the real risk for this business?

One factor per table, with the reason.

Open reports/02-refinement-product-factors.md

Our measured run (open after the debrief)

Measured on 6 November 2026, agentic-qe 3.15.18, Claude Code, unattended: 3.3 minutes, $0.52. The AI agent produced 74 test ideas across the seven SFDIPOT factors, 23 requirement gaps and 11 ranked risks. It did not read the acceptance-criteria file, which is worth asking the room about.

Development: tests for the highest-risk module

Exercise 3 · Development · 14:50–15:10

About 15 minutes · qe-test-architect

Prompt · paste into your AI agent
Use qe-test-architect to generate a comprehensive test file for the payment-retry logic in src/lib/payment-retry.ts. Use the test ideas in reports/02-refinement-product-factors.md as input, and include property-based tests for the module's invariants.
Save the test file as tests/lib/payment-retry.architect.test.ts and a short rationale to reports/03-development-tests.md.
Save learnings and persist patterns.
Save totests/lib/payment-retry.architect.test.tsTwo versions in LAB.md
While it runs

Open src/lib/payment-retry.ts. Name one invariant its tests must hold.

Order matters

This step reads what Exercise 2 wrote. Run them in order.

Exercise 3 debrief

Last 5 minutes of the slot · in pairs, then the room

Development: tests for the highest-risk module

1In the report

Do the generated tests run, and do they pass?

For a failing test, decide whether the test or the code is wrong.

2In pairs

Which invariants did the property-based tests choose?

Look for backoff bounds, retry limits and idempotency.

3In the room

Are those the invariants that matter?

One missing invariant per table.

Run npm test -- --run tests/lib/payment-retry.architect.test.ts

Our measured run (open after the debrief)

Measured on 6 November 2026, agentic-qe 3.15.18, Claude Code, unattended: 3.0 minutes, $0.55. The AI agent wrote 74 tests, all passing, with fast-check property tests. One it.fails test documents that jitter is added after the delay cap. It also recorded that every thrown error is retried, even a card_declined code.

CI/CD: verify, gate, decide

Exercise 4 · CI/CD · 15:10–15:25

About 10 minutes · qe-queen-coordinator

Prompt · paste into your AI agent
Use qe-queen-coordinator to run a verification-only quality assessment of src/lib/payment-retry.ts (do NOT generate tests). Analyse coverage gaps with risk scoring, security-scan the module, apply a 90% quality gate, and give a GO / CONDITIONAL / NO-GO deployment recommendation with the top blockers.
Save the consolidated report to reports/04-cicd-quality-assessment.md.
Save learnings and persist patterns.
Save toreports/04-cicd-quality-assessment.mdTwo versions in LAB.md
While it runs

Read src/lib/payment-retry.ts. Would you ship it? Write down your answer.

Coverage clears 90%

payment-retry.ts is at 100% of statements and 97.29% of branches before Exercise 3 adds tests. After it, 109 of 109 tests pass at 100% coverage. Coverage alone does not make the release call.

Exercise 4 debrief

Last 5 minutes of the slot · in pairs, then the room

CI/CD: verify, gate, decide

1In the report

Which recommendation did you get?

NO-GO, CONDITIONAL or GO. Compare the gate score with the coverage figure.

2In pairs

Did it report the missing idempotency key and the backoff cap applied before jitter?

Both are in the module’s source.

3In the room

Would you ship it?

Show of hands, then what you would be willing to ship without.

Open reports/04-cicd-quality-assessment.md

Our measured run (open after the debrief)

Measured on 6 November 2026, agentic-qe 3.15.18, Claude Code, unattended: 1.4 minutes, $0.34. Verdict in this run: NO-GO with 109 of 109 tests passing at 100% coverage. Blockers: no idempotency key, no gateway timeout, every thrown error retried. The quality_assess gate call returned insufficient evidence, so the AI agent applied the 90% threshold itself.

Self-learning: put the fleet’s memory to work

Exercise 5 · Self-learning · 15:25–15:35

About 10 minutes · same prompt for every tool

Prompt · paste into your AI agent
Recall from AQE memory what the fleet learned about this checkout app across Exercises 1–4: payment retry, cart state, checkout form accessibility, and request validation.

First list what you recalled: each pattern's name and one line on what it says. Then consolidate that into a one-page brief (top risks, testability gaps, contradictions, and the release verdict), framed as either:
  • an onboarding brief for someone joining the project today, or
  • a handoff document for the next person enhancing the checkout app.

Where memory returns nothing for a topic, take it from reports/01 to 04 and label that part REPORTS-BASED.

Save the brief to reports/05-handoff-brief.md.
Save toreports/05-handoff-brief.mdSame prompt for every tool
While it runs

Write down three risks you remember from Exercises 1 to 4, then check the recall.

What the fleet recalls
  • Top risks, ranked across the exercises
  • Testability gaps that block quality work
  • Contradictions between epic, stories and criteria
  • The release verdict and its blockers

Exercise 5 debrief

Last 5 minutes of the slot · in pairs, then the room

Self-learning: put the fleet’s memory to work

1In the report

Does the recalled list name this codebase?

payment-retry.ts, CartContext and CheckoutForm.tsx should all appear.

2In pairs

Which parts of the brief are REPORTS-BASED?

Those topics were not in memory. Compare them with your own reports.

3In the room

Would you hand this brief to the next person on this code?

One thing per table that you would add first.

Open reports/05-handoff-brief.md

Our measured run (open after the debrief)

Measured on 6 November 2026, agentic-qe 3.15.18, Claude Code, unattended: 1.0 minutes, $0.29. Memory returned four patterns from the learning namespace, the same four for every topic. Cart state, form accessibility and request validation came from the reports. A brief built partly from reports is a valid result; it must say so.

Stretch 2b · Exploratory charters from the product factors

Stretch · after the session

About 20 minutes · exploratory-testing-advanced

Prompt · paste into your AI agent
/exploratory-testing-advanced

Using the test ideas in reports/02-refinement-product-factors.md, write three time-boxed exploratory charters for the guest checkout and run a first pass of each against src/app/checkout, src/components/CheckoutForm.tsx and src/lib/. Label every finding EXECUTED, STATIC or INFERRED; list the questions a human must answer.
Save to reports/02b-exploratory-charters.md.
Save learnings and persist patterns.
Save toreports/02b-exploratory-charters.md
Your call

Which charter you would run first, and which findings are evidence rather than guesses.

Stretch 2c · Defect risk profile: where will the bugs be?

Stretch · after the session

About 15 minutes · qe-defect-predictor

Prompt · paste into your AI agent
Use qe-defect-predictor to build a defect risk profile for every module in src/lib/ and src/components/CheckoutForm.tsx from complexity, coupling and coverage (npm run test:coverage). Rank the modules, give the top three risk factors for each with its evidence class, and say whether src/lib/payment-retry.ts belongs at the top of the list, and why.
Save to reports/02c-defect-risk-profile.md.
Save learnings and persist patterns.
Save toreports/02c-defect-risk-profile.md
Your call

Coverage already reads 100% on payment-retry.ts. If it still ranks high, decide whether you agree with the reason.

07Section 0715:35–16:00

Apply

What the swarms prepare, how to interrogate them with PACTS, and a roadmap for your context.

Summary · PACTS · Roadmap · Take-aways

Photo: Mateusz Sobczak / Unsplash

What the swarms prepare, and what you decide

Summary
PhaseOn the board before you sit downStill your call
IdeationQuality criteria, ranked risks, a testability read on every acceptance criterionWhether the epic is ready, and what you refuse to start without
RefinementThe product broken into its factors, with test ideas against each oneWhich factors carry the real risk for this business
DevelopmentRunnable tests for the riskiest module, including its invariantsWhether the invariants it chose are the ones that matter
CI/CDCoverage gaps, a security scan, a gate result, a recommendationThe release call, and what you are willing to ship without
Self-learningA one-page brief consolidated from what the fleet rememberedWhether that is the story you would hand the next person on this code
Nothing in the right-hand column is delegated.

PACTS: five interrogation tools

Apply PACTS · 15:35

Each property is a question, not a definition. Walk it against your reports, score each report 0 to 3 per property in pairs, and use the probe when the answer is thin.

P

Proactive

Did it flag risk before being asked?

“Cite the exact src/ lines that drove your conclusion.”
A

Autonomous

Did it decide what to inspect for itself?

“What is the most important thing you did not look at?”
C

Collaborative

Did the AI agents reference each other?

“Do AI agents A and B agree on the top three risks?”
T

Targeted

Was it fitted to this checkout code?

“Rewrite this for our context, not a generic checklist.”
S

Structured

Can you trace each conclusion to its evidence?

“Show the trail: which AI agent decided this, from which input, and why?”
Compare engines. If your pair has a Claude Code user and someone on another tool, compare the two reports for the same exercise. That gap is the value of the orchestration layer.

A starting point for your context

Roadmap · 15:45–15:55
1 · Install and explore
  • npm install -g agentic-qe@latest
  • aqe init --auto in your own project
  • Browse the skill library
2 · Map one AI agent to one pain
  • Pick your biggest clerical burden
  • Try qe-qx-partner, qe-flaky-hunter, qe-accessibility-auditor
  • Measure time saved in week one
3 · Build the swarm gradually
  • Add AI agents as trust grows
  • Month 1: the AI agent suggests, the human decides
  • Month 4: the AI agent handles low-risk work
Keep it small. One AI agent, one phase, one repository. Two metrics: time saved, and one the business already tracks.

What you take with you

Wrap-up
  • Expert thinking, made accessible without years of investment.
  • A configured, MIT-licensed framework on your own machine. Nothing held back.
  • PACTS as a portable, vendor-neutral evaluation instinct.
  • An adoption roadmap written for your context, not ours.
Resources
  • bit.ly/ttf-agentic-qcsd
  • github.com/fndlalit/TTF-Agentic-QCSD-Workshop
  • github.com/proffesor-for-testing/agentic-qe
  • agentic-qe.dev
  • forge-quality.dev
  • teatimewithtesters.com

QCSD paper: EuroSTAR Huddle · Designed Agency: LinkedIn article

Lalitkumar BhamareDragan Spiridonov

The faster horse won’t save us.

But a thinking team, amplified, will.

bit.ly/ttf-agentic-qcsd · teatimewithtesters.com · forge-quality.dev · agentic-qe.dev

Photo: Mathew Schwartz / Unsplash