oc-qa-ops
Test-strategy designer: owns the test pyramid, coverage budgets, contract-test matrix, and load-test planning — the strategy layer split out of oc-bug-check. oc-bug-check runs the tests in under two minutes at the commit gate; oc-qa-ops decides which tests should exist and where. Writes `.opchain/qa.yaml`, which oc-bug-check's test check reads when present. Use for /oc-qa, /oc-qa pyramid, /oc-qa coverage, /oc-qa contracts, /oc-qa loadplan, /oc-qa audit, "test strategy", "test pyramid", "coverage budget", "what should we test", "contract testing", "plan a load test", "too many e2e tests", "our tests are slow", "test debt", "flaky tests", "unit vs integration". Invoked by oc-app-architect Phase 2 to author 06-testing.md. NOT test execution (oc-bug-check), NOT load-test execution or perf budgets (oc-scale-ops), NOT first-party API conformance authoring (oc-api-dev), NOT writing the tests themselves (the build loop's Generator, or /oc-audit test-bootstrap for untested codebases).
Target: Software development & testing. Automatically collected · unverified.
Excerpt from the author’s documentation
Extracted from a fixed version of SKILL.md in its original language. This is the author’s documentation; installation, compatibility and runtime results have not been verified by this site.
Read the original English text
Topics in the source
- QA Ops
- Command Reference
- /oc-qa pyramid
- /oc-qa coverage
- /oc-qa contracts
- /oc-qa loadplan
- /oc-qa audit
- Checkpoint Integration
On first invocation, read references/orchestrator.md and follow its welcome protocol. QA Ops owns the strategy layer of testing: what tests should exist, at which level of the pyramid, with what coverage, verifying which contracts, under what load. It does not run tests — oc-bug-check does that at the commit gate, CI does it on every PR, and oc-scale-ops executes load tests. QA Ops decides what those runners should be running. The one-sentence split: oc-bug-check answers "do the tests pass?"; oc-qa-ops answers "are these the right tests?" Design the test pyramid for the repo at hand. Not a lecture on testing theory — a concrete, repo-specific allocation: 1. Inventory what exists. Test framework(s), suite shape, counts per level, runtime per level, CI wiring. Read the oc-app-architect and oc-api-dev checkpoints for what the system is supposed to do. 2. Declare the levels for THIS repo (typical: unit / integration / contract / e2e — but a CLI tool, a Worker, and a data pipeline get different pyramids). For each level: what belongs there, what must NOT be tested there, target runtime, and which gate runs it (commit gate / CI / nightly). 3. Allocate. Where should new tests for a given
This is an excerpt. Refer to the complete source and its current requirements.
- Source repository
- asfbay-bit/opchain-skills
- Source file
- plugins/opchain/skills/oc-qa-ops/SKILL.md
- Fixed revision
- 1c7c7bd69a7d875a5dffb419911c24752ca6c285
Sources and evidence
This record was collected automatically. Its documentation, suitability and runtime behavior have not been manually verified.
Author: asfbay-bit/opchain-skills · original repository metadata. Documentation review: Not reviewed. Last source check: 2026-11-10T17:01:26.979Z.
Categories are inferred from names, descriptions and paths. They do not establish compatibility.
License and attribution
Apache-2.0. Third-party content and copyright remain with their authors. Refer to the original license and terms.
Original license ↗Synchronization, copying and user-reported success do not mark a resource as runtime-tested.
Limitations and notes
- Collecting metadata does not mean this site has installed, adapted, runtime-tested or security-reviewed the resource.