test-verification-welding-long

End-to-end welding firmware verification on STM32G4 requires a comprehensive proof plan covering static checks, host unit tests, SIL, on-target, and HIL testing. It applies timing analysis, fault-injection scenarios, and safety validations across the FreeRTOS stack to produce auditable artefacts with defined acceptance criteria.

Fault injection for FreeRTOS firmware on STM32G4 is applied by documenting specific fault-injection scenarios within the verification plan, targeting safety validations and generating traceable timing evidence across host and on-target test environments.

Firmware verification planning explicitly supports the STM32G4 configuration with TIM1 and external ADCs. The strategy develops timing measurements and architecture-level tests that validate the complete welding controller stack interacting with these specific hardware peripherals.

The best way to achieve end-to-end traceability for welding firmware is to establish a formal verification strategy that maps architecture-level tests, fault-injection scenarios, and timing evidence across host, SIL, and on-target environments to auditable acceptance criteria.

Yes, you need docs/PROJECT_CONTEXT.md and docs/TEST_PLAN.md to define test targets, gates, and acceptance criteria. These references provide the necessary project context and test structure required to draft the long-version proof plan and artifact list.