From the source
- 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.






