For QA Team Members
Access your Team CDS, TCP, TSP, and GitHub-Driven TC Sheets in one ecosystem. No new document every sprint — your data is always there, always current, and automatically populated from GitHub and Forge.
QA Automation Backbone One Ecosystem. Every Team. Powered by GitHub + Apps Script
About CDS
Centralized Docs System — The QA Department's Automation Backbone
CDS is a unified ecosystem of interconnected Google Workspace documents, GitHub automation, and Apps Script logic that eliminates repetitive QA paperwork — so your team can focus entirely on testing, investigating issues, and validating features.
1Ecosystem
100%Auto KPIs
0Manual SPDs
All TeamsQA Dept.
What is CDS?
More Than a Document — A Complete QA Automation Ecosystem
CDS is not a single spreadsheet or a standalone tool. It is a network of six interconnected components — all powered by GitHub Actions and Google Apps Script — that work together to eliminate every piece of manual overhead in your QA workflow. From the moment a ticket enters Forge, to the final KPI report for your lead, CDS handles it automatically.
For QA Team Leads
Configure your Team CDS once and let automation take over. KPI calculations, merge request tracking, and historical data are always available — no hunting through archived sprint files or manually summing test case counts.
For Leads & Managers
The Leads - CDS aggregates every team's data in real time. One command center gives you full visibility over manpower, KPIs, test case coverage, and milestone progress across the entire QA department — with no manual aggregation.
The Six Components
Six Interconnected Parts. One Complete Ecosystem.
Every CDS component has a specific role, and each one feeds data into the others. Together they form a self-sustaining automation loop that keeps your entire QA department in sync.
Command Center
Leads - CDS
The master hub that all teams report to. Configure milestones, rosters, and GitHub commands once — and gain live, cross-team visibility with zero manual aggregation.
Living Team Database
Team CDS
One persistent document per team — no new file every sprint. Tickets, test cases, action items, KPIs, and merge requests are pushed in automatically.
Auto-Updated TC Tracking
Test Case Portal (TCP)
Tracks test case statuses and counts per type — UI, Functionality, Security, Performance — always in sync with your TC Sheets. Zero manual updates.
Scenario Status Aggregation
Test Scenario Portal (TSP)
Auto-updates the Master List sheet and tracks scenario statuses across all teams with no manual intervention. A true live registry of your QA coverage.
Automation Backbone
GitHub Engine
The core that processes, distributes, and syncs all data across every CDS component — fetching from Forge, calculating KPIs, and feeding all documents continuously.
Per-Scenario Test Documents
GitHub-Driven TC Sheets
One sheet per test scenario. Auto-numbered steps, auto-updating Table of Contents, and an auto-populating Issues sheet with bug and suggestion data pulled from GitHub.
Problems CDS Eliminates
Built to Remove Every Pain Point in QA Documentation
Every component in CDS was designed to solve a specific, recurring problem that costs QA teams hours every sprint. Here is what CDS permanently eliminates from your workflow.
No More SPDs
Sprint Planning Documents created from scratch every milestone — gone. Team CDS is your persistent workspace that carries data forward automatically.
No More Manual Agile TPs
Agile Test Plans manually built every sprint — eliminated. CDS auto-populates your test plan data from GitHub and Forge in real time.
No More Manual KPI Calc
Hours spent calculating pass rates, test counts, and milestone KPIs — replaced. GitHub Engine computes all KPIs automatically and pushes them to the right place.
No More Status Hunting
Opening five documents to find ticket statuses — over. Every ticket and TC status is fetched from Forge and GitHub and surfaced in your Team CDS automatically.
No More Stale Documents
Old, out-of-date documents from two sprints ago — replaced with a single, always-live CDS that updates continuously in the background.
No More Manual TC Counting
Counting test cases by type for each milestone — done for you. TCP tracks and aggregates every TC count automatically, broken down per category.
How It Works
From Registration to Full Automation — Four Steps
Getting your team onto CDS is simple. Once registered, the ecosystem runs itself — no ongoing maintenance, no manual triggers, no new documents to create at the start of each sprint.
01
Register Your Team
The team lead adds their Team CDS document URL under the UTILS sheet in Leads - CDS. This single action registers the team into the entire CDS ecosystem.
02
GitHub Reads the Config
GitHub reads your team's configuration — members, milestones, linked documents, and Forge project keys — and begins feeding all data automatically.
03
Data Delivered Automatically
Tickets, test cases, merge requests, action items, and KPIs are pushed into your Team CDS, TCP, and TSP without any manual entry from your team.
04
Leads Get Full Visibility
Every Team CDS feeds into Leads - CDS. Leads and project managers get a live, aggregated view of every team's status with no extra work — ever.
Who Is CDS For?
Built for Everyone in the QA Department
CDS is not just for one role. Whether you are writing test cases, managing a sprint, or overseeing the entire QA department — CDS has a component built specifically for your needs.
QA Team Members
Access your Team CDS, TCP, TSP, and TC Sheets. See your assigned tickets, track test case statuses, and log progress — all in one place without creating a new document every sprint.
- Assigned ticket statuses — auto-fetched
- Test case counts per type — auto-calculated
- Action items — auto-identified
- TC Sheets with auto-numbered steps
- Master List of test scenarios
QA Team Leads
Configure your Team CDS once and let the ecosystem handle everything else. KPIs, merge request tracking, and historical data are always there — no hunting through old documents.
- KPI tracking per milestone — auto-calculated
- Merge request & fix tracking
- Full historical data — always accessible
- No more SPD or manual Agile TP
- Team roster & milestone management
Project Leads & Managers
The Leads - CDS gives you a live command center. Monitor every team's status, KPIs, and manpower from a single view — without opening any individual team document.
- Cross-team KPI aggregation — live
- Manpower & task visibility — all teams
- Master List of all test cases across teams
- GitHub command configuration
- Milestone progress across the department
The Ecosystem in Action
Everything Connected. Everything Automatic.
Once your team is registered in Leads - CDS, the entire ecosystem activates. GitHub continuously reads your configuration, fetches data from Forge, calculates KPIs, and pushes results into every connected document — automatically, on every run.
- Auto-fetched Ticket Statuses from Forge
- KPI Tracking Across All Teams
- Master List of All Test Cases
- Team Manpower & Task Visibility
- GitHub Command Configuration
- Merge Request & Fix Tracking
- Action Items — Auto-identified
- Persistent Historical Data
- Milestone-level Test Case Counts
- TC & Script Status Aggregation
- No More SPD or Manual Agile TP
- Cross-team Data Aggregation
CDS — Leads Dashboard
142
Total TCs
18
Action Items
96%
KPI Score
Tickets
Test Cases
MRs
Our Commitment
What You Can Always Count On
CDS is built on reliability. We keep the ecosystem accurate, transparent, and consistent — so your team never has to second-guess whether the data they are looking at is current.
Always Live, Always Accurate
CDS data is not manually entered — it is fetched, calculated, and pushed automatically. What you see is always the current state of your QA work.
Persistent History
Unlike sprint documents that get archived, your Team CDS carries all historical data forward. Every milestone, every test case, every ticket — always accessible.
Built on Google Workspace
No new tools to install. CDS lives in Google Sheets and Docs your team already uses — enhanced by GitHub automation and Apps Script logic that runs silently in the background.
Designed for the Whole Department
CDS scales from a single team to every QA team in the department. One Leads - CDS coordinates all of them — with a consistent, automated standard for everyone.
GitHub-Verified Data
Ticket statuses, merge requests, and test results come directly from GitHub and Forge — the authoritative source. No human errors from copying data between documents.
Continuously Improving
New automations, new document components, and deeper integrations are actively developed. CDS grows with your team's needs and the department's evolving QA processes.
🚀 Powering QA Teams Across the Department with CDS
Focus on What Matters.
CDS handles the repetitive work — status updates, KPI calculations, document creation, data aggregation. You handle the testing. One ecosystem. Every QA stage. Zero overhead.
Auto Status Updates No Manual SPDs KPIs Calculated Automatically All Teams Connected