From Excel Bug Tracking to Full QE Practice: Process Transformation at Capitol AI’s Enterprise Intelligence Platform
Capitol AI converts expert judgment and proprietary data into trusted, auditable outputs for enterprise data teams, financial services firms, and government bodies — all without vendor lock-in or data leakage. We didn’t just test the product. We changed how quality engineering works there.
Enterprise-grade agentic intelligence — built for regulated, high-stakes environments.
Capitol AI is an enterprise-grade agentic intelligence platform designed for organisations where accuracy, auditability, and sovereignty are non-negotiable. It converts expert judgment and proprietary data into trusted, customisable outputs — enabling enterprise data teams, financial services firms, professional services organisations, and government bodies to deploy AI workflows without vendor lock-in or data leakage risk. The platform is model-agnostic, SOC 2 compliant, and supports fully customisable output artifacts. It operates across multiple enterprise clients with independent environments per tenant — meaning that quality validation must account for both platform-level behaviour and client-specific configuration simultaneously. For a platform operating in regulated industries where a single incorrect output can carry significant consequences, quality engineering isn't a checkbox. It's a trust mechanism. The QE team's work at Capitol AI directly supports the reliability that enterprise clients depend on.
We didn't just test the product — we changed how quality engineering works at Capitol AI. Every structural improvement was initiated by the QE team.
At a glance.
Built, structured, scaled.
The engagement moved through three distinct phases — an initial setup period characterised by high defect volume and zero process infrastructure, a process-build phase where every structural improvement was initiated by the QE team, and a scaled testing phase delivering sustained high-volume execution across bi-weekly releases and multiple client environments.
Starting from zero on a live enterprise platform.
When the QE team joined Capitol AI, there was no structured quality engineering process in place. Bug tracking was done informally in Excel. Releases happened without any advance notice to QA. There were no test cases, no feature documentation, no recordings — and the platform was shipping features rapidly across multiple enterprise client environments.
No QA Process or Structure
Informal Excel-based bug tracking with no consistent format, no defect severity classification, and no process for how issues moved from discovery to resolution. The team was starting from zero on a live, enterprise-client-facing platform.
No Release Visibility
Releases went live with no advance notice to QA. The team had no ability to plan test cycles around release windows, meaning defects were often discovered post-release rather than pre-release. This needed to change immediately.
No Test Documentation or Feature Specs
No test cases, no feature matrix, no test plans. Developers were not creating feature documentation or recordings, leaving QA to reverse-engineer expected behaviour from the live product. Every test case had to be authored from scratch.
Rapidly Evolving AI Platform
Capitol AI ships new features and deprecates old ones frequently. Keeping test coverage aligned with a fast-moving enterprise AI product — while simultaneously building the process infrastructure — required continuous documentation discipline and close developer communication.
Every structural improvement was initiated by QE.
The team didn't just test the product — they built the quality engineering foundation that Capitol AI now operates on. From defect workflow design to documentation culture, every structural change was driven and delivered by the QE team.
Built Test Documentation from Scratch
251+ structured test cases across 13+ product modules, built from ground-level product understanding. A full feature map was created first to establish coverage priority, then test cases authored to cover normal, edge-case, and multi-client scenarios across the platform.
Migrated Defect Tracking from Excel to Jira
The team designed and implemented a structured Jira workflow for defect tracking — replacing the informal Excel-based system entirely. Defects now have consistent severity ratings, reproduction steps, environment context, and a traceable history from discovery to closure.
Established Release Communication Process
Worked with the Capitol AI engineering team to define release windows and processes for QA advance notice. QA now receives release plans in advance — enabling structured pre-release test cycles rather than reactive post-release defect discovery.
Introduced Feature Documentation Practice
Drove the adoption of developer-created feature recordings and test plans, using Confluence as the documentation hub. This shifted the burden of requirements interpretation from QA inference to documented developer intent — reducing ambiguity and improving test coverage quality.
Structured Dev–QA Retest Workflow
Defined a clear, consistent process for how developers pick up resolved defect tickets, implement fixes, and return them to QA for retest. This eliminated the informal back-and-forth that had previously created delays and duplicate effort.
Sustained High-Volume Multi-Client Testing
4,373 test executions in Q3 alone across 46 release cycles, covering multiple client environments including EY and Plexal. QA Wolf automation collaboration initiated to identify automatable test cases and begin building an automation layer on top of the manual QE foundation.
The numbers.
Total Defects Raised
Q3 Test Executions
Structured Test Cases
Release Cycles Supported
What changed.
Total Defects Raised
Across the full engagement — spanning Q1 baseline discovery through Q2 process build and Q3 scale phases.
Test Executions in Q3
Delivered in a single quarter across 46 bi-weekly release cycles and multiple enterprise client environments.
Test Cases Created
Built from scratch across 13+ product modules — from feature mapping through edge-case authoring and multi-client scenario coverage.
Release Cycles Supported
Bi-weekly cadence across Q3, each with a defined QA plan, structured pre-release cycle, and documented defect history.
From Zero Structure to Full QE Practice
Excel bug tracker to Jira; no release notice to defined release windows; no docs to Confluence hub — every structural change initiated by QE.
Migration Owned Entirely by QE
The defect tracking migration — from design to implementation to adoption — was driven and delivered by the QE team, not the engineering organisation.
The stack.
The Capitol AI engagement is a story of QE-led process transformation. The team didn't just test the product — they changed how quality engineering works at Capitol. From driving the migration to Jira, to establishing release communication norms, to introducing documentation culture, to structuring the dev–QA retest workflow — every structural improvement was initiated and delivered by the QE team. The result is a quality engineering practice that can sustain 4,373 executions per quarter, support 46 release cycles, and continue to evolve as the platform grows.