Menu
Detailed DSP QA harness-first testing workflow for APC plugins.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
| name | skill_testing |
| description | Detailed DSP QA harness-first testing workflow for APC plugins. |
Title: SKILL: TESTING (DSP QA HARNESS FIRST) Document Type: Skill Author: APC Codex Created Date: 2026-02-18 Last Modified Date: 2026-03-01
Goal: Run APC testing through the audio-dsp-qa-harness workflow first, then host/plugin checks.
plugins/[Name]/qa/, not only harness-side temporary scenarios.plugins/[Name]/qa_output/suite_result.json for machine-readable pass/fail.plugins/[Name]/TestEvidence/test-summary.md with harness, QA runner, pluginval, and DAW smoke outcomes.exit_code and crash_report_path evidence./test verdict is PASS only when harness sanity and plugin-owned suite both pass.Resolve harness path in this order:
$env:APC_DSP_QA_HARNESS_PATHJoin-Path $HOME "Documents/Repos/audio-dsp-qa-harness"Fail fast if the directory is missing.
$HarnessPath = if ($env:APC_DSP_QA_HARNESS_PATH) {
$env:APC_DSP_QA_HARNESS_PATH
} else {
Join-Path $HOME "Documents/Repos/audio-dsp-qa-harness"
}
if (-not (Test-Path $HarnessPath)) {
Write-Error "audio-dsp-qa-harness not found. Set APC_DSP_QA_HARNESS_PATH or install at $HarnessPath"
exit 1
}
cmake -S "$HarnessPath" -B "$HarnessPath/build_test" -DBUILD_QA_TESTS=ON -DCMAKE_POLICY_VERSION_MINIMUM=3.5cmake --build "$HarnessPath/build_test"ctest --test-dir "$HarnessPath/build_test" --output-on-failuresimple_scenario_runner.cpp or suite_runner.cpp).
*${PluginName}*qa*, *${PluginName}*suite*qa* under build/.plugins/[Name]/qa/.
$HarnessPath/scenarios/examples/ and templates in $HarnessPath/examples/templates/.result.json, summary files, WAV artifacts), then update status.json test flags.pluginval is an AppKit app and must run in a GUI login session.SIGABRT and stack frames around HIServices _RegisterApplication / NSApplication sharedApplication,
treat this as an environment bootstrap failure (headless/sandbox context), not a plugin regression./test. Mark validation.pluginval_results.environment_blocked = true, set blocked_reason,
record exit_code/crash_report_path if available, and keep validation.tests_passed tied to harness+QA verdict.open -na /Applications/pluginval.app --args --strictness-level 5 --timeout-ms 30000 --validate "<path-to-plugin.vst3>"Documents/APC_CRASH_REPORT.txt and correlate with QA artifacts.When testing backlog lanes, enforce replay tiers from Documentation/backlog/index.md:
T1 dev loop default,T2 candidate gate,T3 promotion gate,T4 sentinel only when explicitly requested.For heavy wrappers, prefer targeted reruns before broad sweeps and record any owner-approved cadence override in evidence notes.
Documentation governance skill for metadata compliance, ADR hygiene, invariant traceability, and validation evidence logging.
SDLC-aware documentation cleanup and governance specialist for de-bloating repos, consolidating source-of-truth docs, enforcing freshness ownership, aligning implementation docs with ADRs, and automating git artifact hygiene (tracked ignored files, stale archives, and history bloat audits).
Swift companion platform and Apple API ownership for LocusQ. Use when user requests AirPods workflows, CoreMotion motion capture, ear-photo/depth capture, privacy-retention policy, or Apple API boundary decisions for BL-057/BL-058.
End-to-end AUv3 support workflow for LocusQ. Use when user requests AUv3 format enablement, app-extension architecture, JUCE integration boundaries, AUv3 host validation lanes, or cross-format parity decisions.
SDLC-aware documentation cleanup and git artifact hygiene for LocusQ. Use when user requests de-bloating docs, consolidating source-of-truth files, fixing stale ADR alignment, backlog/runbook clarity passes, or git tree artifact cleanup.
Companion runtime state-machine and diagnostics for LocusQ head-tracking. Use when user requests readiness/sync gating, axis/frame sanity checks, pose freshness validation, or deterministic operator diagnostics for BL-053/BL-058.