APZTMS

Daily quality desk.

Connect the application, review what is missing, check a change before QA, work the queue, then offer a draft. APZQEP remains the court of record. This page does not invent a price or a go-live badge.

Connect what already exists.

Source first. Documents next. The desk records the option — it does not invent an inventory or store secrets.

GitHubgithub.com, Enterprise, or a customer host / IP. HTTPS, SSH, PAT, username/password, or PEM. Bind the secret with a credential reference.GitLabgitlab.com or self-hosted. Same connect methods. No clone yet.Azure DevOpsdev.azure.com or visualstudio.com. Method recorded only.BitbucketCloud or self-hosted Git. Same five reach methods.HTTPS or SSH GitAny Git host — domain or IP. git@10.8.1.20:org/app.git or https://git.customer.internal/org/app.git. Source is not cloned here.ZIP uploadArchive received. Unpack lists files by name. Not services or screens.Local folder agentThe Ubuntu agent lists folders. QA picks one. APZTMS does not search /home or the customer LAN.Documentation uploadBRD, FRD, FSD, SRS, NFR, architecture, API, OpenAPI, Swagger, stories, Confluence, Visio, Word, PDF, Excel. pdf, docx, xlsx, csv, md, txt, json, yaml, html, drawio, vsdx, zip.

Five verbs. Not a second QEP.

Primary tabs only. Graph, agents, and settings stay in More.

ConnectWhere is the application?ReviewWhat did we find?CheckDid tests on this source fail?QueueWhat should QA look at next?ReadyAdvisory only — should we hand this to APZQEP?

Also in the suite

Same family. Different jobs. Marketing only.

APZQEPCertify with a human GO. TMS never writes that record.APZPENScoped security work when the threat model demands it.APZPRDConnected work for the teams building the product.