qaas

Plugin qaas from marketplace qaas-copilot in eldarush/qaas-copilot. Commands read from the repo's manifest — 1 month ago.

Skills (20)

• analyze-existing-tests

  Build a behavioral inventory of existing tests and a coverage-gap diff against the SUT surface catalog.

• analyze-helm-k8s

  Derive effective runtime config from Helm charts or K8s manifests; produce runtime-config.md with file:line citations.

• analyze-sut-repo

  Extract test-relevant facts from a user-provided SUT source repository; produce a structured sut-profile.md with file:line citations.

• author-custom-hook

  Write a QaaS custom hook (Generator, Assertion, Probe, or TransactionProcessor) with correct base-class signatures and config records.

• author-mocker-yaml

  Write a valid QaaS mocker YAML (Servers/Stubs/Controller) that serves stubbed HTTP responses.

• author-runner-yaml

  Write a complete, drift-correct QaaS Runner YAML covering all sections from MetaData through Assertions.

• build-mocker-image

  Build and verify a Docker image for a custom QaaS mocker using the multi-stage aspnet:10.0 Dockerfile.

• choose-action-type

  Maps a testing intent to the correct QaaS session action type (Publisher/Consumer/Transaction/Collector/Probe/MockerCommands).

• diagnose-failure

  Triage a QaaS test failure using exit code, allure result JSONs, and the error-signature table.

• document-test-project

  Produce a structured README.md for a finished QaaS test project so others understand what is tested and how to run it.

• offline-packaging

  Configure a QaaS project to restore packages and install templates from a local Artifactory feed with no internet access.

• pick-assertion

  Select the correct assertion from the 11 available; fetch exact AssertionConfiguration keys from live docs.

• pick-generator

  Select the correct generator from the 11 available; fetch exact GeneratorConfiguration keys from live docs.

• plan-test-sprint

  Decompose a user testing goal into a validated sprint.json with priority-ordered, mechanically-verifiable tasks.

• qaas-overview

  Master QaaS guide. ALWAYS read this FIRST for ANY QaaS test work — planning, writing Runner or Mocker YAML, custom C# hooks, running/collecting results, or debugging failures. Loads the QaaS Constitution, the doc-drift traps, the skill index, how to fetch live docs over curl, and how to read the off

• run-and-collect

  Execute QaaS CLI verbs (run/act/assert/execute/template) and collect allure-results artifacts.

• scaffold-mocker-project

  Scaffold a QaaS Mocker project with correct csproj, Dockerfile (aspnet:10.0), and YAML copy settings.

• scaffold-runner-project

  Scaffold a QaaS Runner project with correct csproj, NuGet.config, and YAML copy settings.

• validate-compatibility

  Validate every QaaS field, package version, and feature reference against the Fact Base (s13, s14) and live docs before authoring any file. Rejects deprecated left-column drift forms and non-existent features. Use whenever you are unsure whether a field, version, or config key exists in the current

• verify-done

  Mechanical completion gate — execute every verify[] step from the sprint task and produce a verdict JSON.

Slash commands (5)

• /qaas:diagnose

  Diagnose a failing QaaS test from its exit code, allure results, and logs using the error-signature table.

• /qaas:docs

  Fetch a QaaS documentation page from the configured docs mirror over curl (airgap-friendly, no WebFetch).

• /qaas:fact

  Print an offline QaaS Fact Base slice (s00..s15) bundled with the plugin — drift-corrected, no network needed.

• /qaas:new-test

  Drive a full QaaS test from a one-sentence goal — plan, scaffold, author YAML, run, and verify with evidence.

• /qaas:verify

  Run the fail-closed QaaS completion gate — execute every verify step and emit a PASS/FAIL verdict with evidence.

Subagents (4)

• qaas-analyst

  Read-only analysis subagent. Invoke when the user provides SUT source repos, Helm charts, K8s manifests, or existing test files that need to be analyzed before planning. Runs analyze-sut-repo / analyze-helm-k8s / analyze-existing-tests in an isolated context and returns ONLY a structured summary plu

• qaas-debugger

  Use to root-cause a failing QaaS test from exit codes, allure result JSONs, and logs, then propose and verify the minimal fix. Invoke when a run exits non-zero or produces failed/broken assertions. Evidence-driven; never claims a fix without a fresh green run.

• qaas-planner

  Use to turn a QaaS testing goal into a validated, priority-ordered plan with a per-task done-contract BEFORE any code is written. Invoke when the user describes a system to test and wants a sprint/plan. Questions every ambiguity; never writes test files itself.

• qaas-test-author

  Use to implement a QaaS test from an agreed plan/contract — scaffolds the Runner/Mocker projects, writes drift-correct .qaas.yaml / .mocker.yaml, custom C# hooks, and test data, then builds and runs to prove it. Invoke after a plan exists. Emits complete files only; verifies with real command output

Hooks (1)

• SessionStart

  cat "${CLAUDE_PLUGIN_ROOT}/skills/qaas-overview/SKILL.md"

Similar plugins