harness-test-verification

Verifies MIL-STD-1553B harness implementations and writes test code and Korean test documents.

Updated Nov 22, 2023
One-click install
npx skills add https://github.com/parksanghoon-sys/TestCode --skill harness-test-verification-parksanghoon-sys
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: harness-test-verification
Source: https://github.com/parksanghoon-sys/TestCode/tree/main/src/MIL-STD-1553B/.agents/skills/harness-test-verification
Command: npx skills add https://github.com/parksanghoon-sys/TestCode --skill harness-test-verification-parksanghoon-sys

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve? After implementing MIL-STD-1553B harness features, teams often skip systematic verification or leave test documentation incomplete. This Skill ensures every finished implementation is verified against protocol-specific scenarios and that test code plus Korean-language test documents are produced or updated together. ## Core Features & Use Cases - Protocol-Specific Verification Checklist: Covers BC/RT/BM message flows, Command/Status/Data Word handling, Subaddress and Mode Code processing, Bus A/B switching, timeouts, retries, and error injection. - TDD Traceability: Enforces Red/Green/Refactor evidence by confirming failing tests actually fail, pass after fixes, and survive regression after refactoring. - Standardized Test Documentation: Generates test plan and result documents under docs/test/ using a provided Korean template with scenarios, expected vs. actual results, and risk sections. - Use Case: After implementing RT-to-RT relay handling, use this Skill to add missing unit and integration tests, verify bus-switching and timeout behavior, and produce a dated test result document in Korean. ## Quick Start Verify the completed MIL-STD-1553B harness feature, add missing tests for bus switching and error injection, and write the test plan and result documents in Korean.

Frequently Asked Questions about harness-test-verification

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I test a MIL-STD-1553B harness implementation?▼

Verify BC-to-RT, RT-to-BC, and RT-to-RT message flows, then check Command Word, Status Word, Data Word counts, Subaddress, and Mode Code handling. Also test Bus A/B switching, timeouts, retries, and error injection with recovery.

What test scenarios are required for MIL-STD-1553B protocol verification?▼

Required scenarios include normal and abnormal message flows, bus switching between Bus A and Bus B, timeout handling, retry logic, Mode Code processing, and error injection with recovery. Log and trace verification is also mandatory.

How do I write a MIL-STD-1553B test plan document?▼

Use the provided Korean template covering test target, environment, scope, scenario list, input conditions, expected results, log checkpoints, actual results, failure analysis, and risks. Save it as docs/test/YYYY-MM-DD_feature_test-plan.md.

Does this Skill support both native and .NET test code?▼

Yes, test outputs are organized under tests/native/ and tests/dotnet/ directories, so both C/C++ and C# harness implementations can be verified. The same protocol checklist applies to both stacks.

Why should failing tests be confirmed to actually fail before fixing?▼

Confirming a failure-reproduction test actually fails proves the test detects the defect rather than passing vacuously. This preserves TDD Red/Green/Refactor evidence and prevents false-positive regression coverage.