QA Documentation Hub One Hub. Every QA Doc. Always In Sync

Work Smarter. Test Better.

The Centralized Docs System (CDS) is the QA Department's documentation ecosystem at Channel Info Tech | HQZen.com. It connects all your Google Sheets, Google Docs, Apps Script, and GitHub into one centralized system — eliminating repetitive manual work so your team can focus on what truly matters: actual testing, investigating issues, and validating features.

1Central Hub

8Components

0Manual SPDs

All TeamsManual & Auto QA

Auto Doc Updates

Auto KPI Calculation

No More SPDs

Auto Email Reports

GitHub-Driven Docs

KPI-Based Performance

I'm a QA Team MemberAccess your Team CDS, TCP, TSP & TC Sheets →

I'm a Lead / ManagerOpen Leads - CDS for full team visibility →

Explore the Ecosystem

CDS Components at a Glance

Eight interconnected components — all built on Google Workspace, GitHub, and Apps Script — forming one complete QA documentation ecosystem for Manual and Automation QA teams.

Live Activity

Documents Updated Right Now

Real-time view of active CDS documents across all QA teams.

No active documents right now. Check back soon!

How Components Connect

The CDS Ecosystem

Every component in CDS is interconnected. Data flows automatically between Google Workspace documents, GitHub, and Apps Script — no manual handoffs, no copy-pasting, no duplication.

Leads - CDS

Command Center

The master hub that all teams report to. Source of all dropdown data, master roster management, and GitHub document sync configuration for the entire QA department.

Team CDS GitHub Engine Dashboard

Team CDS

Living Team Doc

Each team's persistent QA workspace — replaces SPD and Agile TP. Auto-populated with tickets, test case counts, action items, and merge request tracking.

TCP TSP TC Sheets

GitHub Engine

Doc Sync Core

The connector that reads configurations, distributes data, and keeps all Google Workspace documents in sync. Fetches from Forge, calculates KPIs, feeds all CDS documents.

TC Sheets TCP TSP Apps Script

Google Apps Script

Logic & Automation

Powers triggers, auto email reports, KPI calculations, and document-level logic across the entire ecosystem. The engine behind automated reminders and scheduled updates.

Leads - CDS Team CDS GitHub

Test Case Portal

TCP — Auto-updated

Auto-tracks test case status and counts per type across all teams. UI, Functionality, Security, Performance — always in sync with TC Sheets via GitHub.

TC Sheets Team CDS GitHub

Test Scenario Portal

TSP — Auto-updated

Auto-updates the Master List sheet and tracks scenario statuses across all teams. No manual updates, no copy-pasting, no stale data — ever.

TC Sheets Team CDS GitHub

TC Sheets

GitHub-Driven

One Google Sheet per test scenario. Auto-numbered steps, auto-updating Table of Contents, and auto-populating Issues sheet with bug and suggestion data from GitHub.

GitHub TCP TSP

Leads - Dashboard

KPI & Visibility

Live aggregated view of all team progress, KPIs, manpower, tasks, and documentation status — fed automatically from every Team CDS with zero manual effort.

Leads - CDS Team CDS

Not sure where to start? Reach out to your QA lead or check the CDS documentation to find the right onboarding path for your team.

Everything Connected

One Hub. Every QA Stage.

From writing a test case to tracking KPIs across all teams — CDS centralizes every document, every update, and every report in one connected Google Workspace ecosystem.

Leads - CDS: Command Center

The central hub for all team documentation. Provides dropdown data, master rosters, KPI tracking, and commands GitHub on what documents to update and when.

Team CDS: Living Document

Each team's persistent QA workspace. No new document every sprint — data auto-updates with tickets, test cases, action items, and merge requests from GitHub.

Test Case Portal (TCP)

Auto-tracks test case status and counts per type — UI, Functionality, Security, Performance. Always in sync with your TC Sheets via GitHub.

Test Scenario Portal (TSP)

Auto-updates the Master List sheet and tracks scenario statuses across all teams — no manual updates, no copy-pasting, no stale data.

GitHub — Doc Sync Engine

The connector that reads configurations, distributes data, and keeps all Google Workspace documents in sync. Fetches from Forge, calculates KPIs, and feeds all CDS documents.

GitHub-Driven TC Sheets

One Google Sheet per test scenario. Auto-numbered steps, auto-updating ToC, and auto-populating Issues sheet with bug and suggestion data pulled from GitHub.

How It Works

Your Journey with CDS

Simple onboarding whether you're a QA team member or a lead setting up the documentation ecosystem for your whole department.

Register Your Team

The team lead adds their Team CDS document under the UTILS sheet in the Leads - CDS. This registers the team with the entire CDS ecosystem.

GitHub Syncs Your Documents

GitHub reads your team's configuration — members, milestones, and linked Google Workspace documents — and begins feeding data automatically across all connected sheets.

Data Populated Automatically

Tickets, test cases, merge requests, action items, and KPIs are pushed into your Team CDS — no copy-pasting, no manual entry, no creating new documents every sprint.

Leads Get Full Visibility

Every Team CDS feeds into Leads - CDS. Leads get a live, aggregated view of all team progress, KPIs, and documentation — with zero extra effort.

What the Team Says

Real Teams. Real Results.

QA teams across the department have already made the shift to CDS — and the difference in documentation overhead speaks for itself.

CDS completely eliminated our sprint document creation overhead. Ticket statuses, KPIs, and test case counts are all there automatically. We just focus on actual testing now.

QA LeadDocumentation & ReportingCDS — All Teams

Having a single Leads - CDS that aggregates all teams in real time is a game-changer. I no longer need to open five documents to check progress — all reporting is right there, live.

Project ManagerVisibility & PlanningQA Department — HQZen

The GitHub-Driven TC Sheets auto-number my steps, update my ToC, and push data to TCP and TSP automatically. What used to take hours of manual work is now instant.

QA EngineerManual & Regression TestingGitHub-Driven TC Sheets

Leads - CDS Command Center

Every QA Document Your Department Needs — All in One Place.

Once your team is registered, the Leads - CDS becomes your live documentation control tower. No extra tools, no manual aggregation, no creating new documents at the end of every sprint. Just one centralized hub that keeps your entire QA department connected, documented, and measured.

Auto-fetched Ticket Statuses from Forge
KPI-Based Performance Measurement
Master List of All Test Cases
Team Manpower & Task Visibility
GitHub Document Sync 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
Auto Email Reminders & Reports

CDS — Leads Dashboard

142

Total TCs

Action Items

96%

KPI Score

Tickets

Test Cases

MRs

🚀 QA Documentation Hub — Channel Info Tech | HQZen.com

Focus on What Matters.

CDS handles the repetitive documentation work — status updates, KPI calculations, report generation, email reminders, and data aggregation. You handle the testing. One centralized hub. Every QA stage. Zero overhead.

Auto Doc Updates No Manual SPDs KPIs Calculated Automatically Built for QA Teams