hsb-test
Execute QA test plans on Holoscan Sensor Bridge hardware. Reads a user-provided test document, filters tests by the user's setup, determines which tests can run automatically, executes them with pass/fail evaluation, and produces a structured test results report.
Security Assessment
About hsb-test
This skill executes QA test plans against NVIDIA Holoscan Sensor Bridge hardware. It reads a user-provided test document (a local file or web link), filters the tests to those runnable on the user's specific platform, board, and sensor configuration, determines which can run automatically versus manually, executes the automatable ones with pass/fail evaluation, and produces a structured test results report. It solves the problem of turning a written QA test plan into a repeatable, hardware-aware automated test run.
The workflow is interactive and gated. It requires SSH_TARGET and REMOTE_ROOT, presents a phase plan, and will not proceed until the user supplies a test document and confirms. Phase 0 verifies devkit SSH reachability, pings the HSB board, and checks demo container availability, reading FPGA version and board identity; Phase 1 obtains and studies the test plan and the repository's examples directory to build an executable, filtered test list, skipping manual tests and those needing extra equipment; Phase 2 runs each test in sequence inside the demo container, evaluates pass/fail against the plan's criteria, logs results, and on failure analyzes logs and suggests fixes while letting the user decide how to proceed; Phase 3 produces a report that can be saved; and Phase 4 cleans up containers, temporary files, and session state. A session fast-path skips re-verification when prior state exists, and Phase 0 is re-run on connectivity-loss symptoms or on user request.
It targets NVIDIA Holoscan QA engineers and hardware developers who need to validate sensor bridge boards against documented test plans. It assumes the devkit is already set up and offers to invoke the hsb-setup skill if not. Model invocation is disabled and it runs only when explicitly invoked. A benchmark documents that it passed NVIDIA's NVSkills-Eval.
FAQ
What input does it need?
A test plan document, provided as a local file path or a URL. It stops and asks for this before proceeding, and also needs SSH_TARGET and REMOTE_ROOT set.
Does it run every test in the document?
No. It filters tests to the user's platform, board, and sensor setup and classifies them as automatable or manual, running only the automatable ones and skipping manual tests and those requiring additional equipment.
How are results evaluated and reported?
Each test is run in sequence and evaluated pass/fail against the criteria in the test plan, with results logged. It then produces a structured results report with per-test status, issues, and fixes, which can be saved to a file.
What if the devkit isn't set up yet?
It assumes SSH, the demo container, host configuration, and a connected board are ready, and if setup is incomplete it offers to invoke the hsb-setup skill first.
Does it clean up after itself?
Yes. Phase 4 cleans up all test artifacts including containers, temporary files, and session state.
Install hsb-test
Quick Setup:
- Copy the skill folder to
.claude/skills/ - Claude will automatically detect and use the skill
Repository
nvidia/skills