Test execution — functional & non-functional

/qa:ci

End-to-end red-build triage

Pull the whole failing build (any CI), bucket every failure, fix the fixable causes, harden to green ×3, and escalate real defects.

USAGE/qa:ci ['x' or 'full' for the extended stability + full-suite gate] [build/run URL | build number | 'last']
Test execution — functional & non-functionalCTFL v4.0 §1.4 · §2.2 · §5.5 · §6 · Quality in DevOps (Specialist) · CT-TAEAutomation

What it does

The build-wide CI orchestrator: pulls the whole latest red build on any platform, triages every failure into a bucket (test defect / product defect / environment / flaky), fixes the test/env/flake causes and confirms each locally, hardens fixed tests to green ×3, and escalates real product defects without masking them. The 'x'/'full' mode adds a mandatory-stability + full-suite local gate. Never commits, pushes, or triggers CI unless asked.

When to use it

After a red build, to triage and fix the whole build end-to-end in one pass — not just one log.

Prerequisites

qa.config.yml with ci.platform (+ jenkins_url/jenkins_job & JENKINS_USER/JENKINS_API_TOKEN, or gh for GitHub Actions) — or a build URL — or local JUnit artifacts; the configured runner.

Output

ISO/IEC/IEEE 29119-3 Test Execution Log / Test Results -> reports_dir/CI-TRIAGE-LOG-<date>.md, with product defects raised as Incident (Defect) Reports via /qa:triage.

Mechanics

How it works

  1. Read config; parse mode (plain vs extended) and build reference
  2. Pull the failing set by precedence (arg URL -> configured CI -> local artifacts); state N
  3. Triage each failure into one bucket (A test / B product / C env / D flaky)
  4. Fix the fixable causes (A + fixable C) with the smallest trace-rooted change; confirm locally
  5. Harden each fixed test to green ×3 (hard gate in extended mode)
  6. Escalate Bucket-B product defects via /qa:triage; never mask
  7. Report counts; in extended mode verify the full local suite

Why it works

The theory behind it

Quality in DevOps + confirmation testing + defect management (CTFL §1.4, §2.2, §5.5). Honesty rule = Principle 1: a defect is escalated, never masked; a green build you can't trust is worse than a red one.

CTFL v4.0 §1.4 · §2.2 · §5.5 · §6 · Quality in DevOps (Specialist) · CT-TAE

Example

See it in use

ci
> /qa:ci x

✓ Correct when It pulls the whole build's failures, fixes only test/env/flaky ones, reports stability as n/3 (not prose), escalates product defects instead of masking, and never commits/triggers CI unless asked.

Related commands

/qa:fix-ci/qa:fix-jenkins/qa:flaky-hunt/qa:triage

Used by

Automation