# Amazon — How TCS built an agentic test orchestrator with Amazon Bedrock AgentCore

- Company: Amazon (amazon.com)
- Announced: 2026-11-10T16:59:43+00:00
- Category: not stated
- Coverage: not counted
- Announcement: no
- Group: routine
- Source: https://aws.amazon.com/blogs/machine-learning/how-tcs-built-an-agentic-test-orchestrator-with-amazon-bedrock-agentcore/
- Record: https://forck.live/items/34118-how-tcs-built-an-agentic-test-orchestrator-with-amazon-bedrock-agentcore
- Subject: Bedrock / Nova

Tata Consultancy Services built an agentic test orchestrator on Amazon Bedrock AgentCore to speed up testing for its banking, financial services and insurance clients, where the slowest part of a release is the work after code is written. TCS says the goal was not to replace quality engineers but to remove repetitive translation and execution work so engineers could spend more time on risk analysis, exploratory testing and release decisions. The platform decomposes testing into specialized tasks, each with its own agent, tools, validation rules and context, with a deterministic supervisor routing work and an execution workflow controlling retries, error classification, persistence and reporting. TCS chose AgentCore for three reasons: Amazon Bedrock's choice of models lets each agent use the model that fits its task, the AgentCore runtime scales with demand without TCS provisioning or tuning agent servers, and each session runs in its own isolated microVM for session-level separation in the multi-tenant platform. Testers supply requirements through Jira stories, business requirement documents, Swagger specifications, uploaded documents, GitLab source folders or captured UI flows, and the platform generates test scenarios, Gherkin feature files and executable Java or Python tests. Tests run on Amazon ECS, results are stored in Amazon S3 and Amazon DynamoDB, and each tenant gets its own Kubernetes namespace, Amazon Cognito user pool, AWS KMS key, S3 bucket, DynamoDB tables and Amazon Bedrock Knowledge Bases.

## Evidence

Verbatim from https://aws.amazon.com/blogs/machine-learning/how-tcs-built-an-agentic-test-orchestrator-with-amazon-bedrock-agentcore/:

> This post was co-written with Varun Valsan from Tata Consultancy Services (TCS).
> 
> Tata Consultancy Services (TCS) runs large-scale testing for Banking, Financial Services, and Insurance (BFSI) clients, where the slowest part of a release is rarely writing application code. The larger constraint is the chain of work that follows: interpreting requirements, designing scenarios, writing and maintaining automation, preparing execution environments, investigating failures, and assembling evidence for review.
> 
> BFSI clients need to increase testing throughput while preserving the controls expected in financial services. The objective wasn’t to replace quality engineers. It was to remove repetitive translation and execution work so that engineers could spend more time on risk analysis, exploratory testing, and release decisions. These industry needs generated four specific requirements for TCS. First, every test must be grounded in project-specific context rather than generic prompts. Second, it had to cover both API and browser-based UI testing to match how BFSI applications are built. Third, security is paramount, so every tenant’s data and knowledge store must be isolated.

---

Record: https://forck.live/items/34118-how-tcs-built-an-agentic-test-orchestrator-with-amazon-bedrock-agentcore
Catalogue: https://forck.live/llms.txt
Current issue: https://forck.live/feed.md
