Artificial Intelligence1 min read

How TCS built an agentic test orchestrator with Amazon Bedrock AgentCore

By · Published by Everything Blog

In short

The multi-tenant cloud system relies on specialized artificial intelligence agents running within isolated microVM environments to guarantee security across enterprise sessions. Testing inputs are ingested directly from existing workflow tools like Jira and GitLab before being converted into actionable tasks. Amazon Elastic Container Service runs the generated tests, while logs and operational data are preserved across Amazon S3 and DynamoDB. This setup allows engineering teams to minimize repetitive failures and accelerate release timelines without replacing human oversight.

Key points

  • Quality engineering teams can eliminate repetitive maintenance work to focus directly on…: Quality engineering teams can eliminate repetitive maintenance work to focus directly on release decisions and risk analysis.
  • The platform enables dynamic model selection, applying distinct foundation models optimiz…: The platform enables dynamic model selection, applying distinct foundation models optimized for specific tasks like code generation or scenario design.
  • Comprehensive cloud infrastructure leverages Amazon ECS for test execution alongside Dyna…: Comprehensive cloud infrastructure leverages Amazon ECS for test execution alongside DynamoDB and S3 for persistent data management.

Sources checked by our analysis pipeline: 1

Artificial Intelligence

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.…

Artificial Intelligence