test-verification-welding-short

Define measurable verification requirements for welding power supply firmware changes.

Updated Jan 30, 2026
One-click install
npx skills add https://github.com/AntonBespalov/WC_IST --skill test-verification-welding-short
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-verification-welding-short
Source: https://github.com/AntonBespalov/WC_IST/tree/main/.codex/skills/test-verification-welding-short
Command: npx skills add https://github.com/AntonBespalov/WC_IST --skill test-verification-welding-short

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Short, essential guidelines for testing and verification of welding power supply firmware, focusing on measurable requirements, proof plans, fault-injection, and safe-state checks. It references canonical project documents and enforces timing and hardware-path verification, including BKIN-related paths.

Core Features & Use Cases

  • Defines compact, auditable verification tasks for control/measurement/safety changes.
  • Emphasizes separation of logic and HAL, measurable criteria, and fault-injection coverage.
  • Provides references to welding-safety-core and welding-verification-core for concrete test content.

Quick Start

Consult welding verification core references and run a basic timing fault-injection test on the BKIN path to validate safety paths.

Frequently Asked Questions about test-verification-welding-short

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

FAQPage Schema
How do I define measurable verification requirements for welding power supply firmware?

Measurable verification requirements for welding power supply firmware are defined by creating compact, auditable tasks that enforce timing checks, fault-injection coverage, and safe-state validation for control, measurement, and safety changes.

What is the best way to test BKIN hardware paths and safety states in STM32G4 firmware?

Testing BKIN hardware paths in STM32G4 firmware involves running a basic timing fault-injection test to validate safety states, ensuring strict separation between application logic and HAL layers while verifying measurable acceptance criteria.

How do I create a proof plan for fault-injection testing in welding firmware?

A proof plan for fault-injection testing in welding firmware is created by separating logic from HAL, defining measurable goals, and applying targeted fault-injection to validate timing constraints and hardware safety paths.

When do I need measurable acceptance criteria for welding safety changes?

Measurable acceptance criteria for welding safety changes are needed when modifying control, measurement, or safety systems, ensuring that timing, fault-injection, and hardware-path verification requirements are satisfied and auditable.

Does this welding verification guidance cover instrumentation and fault-injection coverage?

Yes, this welding verification guidance satisfies requirements for measurable goals, proof plans, acceptance criteria, fault-injection, and instrumentation by referencing canonical project documents for concrete test content.