The latest articles on DEV Community by Rishu (@rishumishra). https://dev.to/rishumishra https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3916264%2Fec70aa3d-5f3c-48b6-8363-2dfa14fdd8b8.png https://dev.to/rishumishra en Rishu Wed, 06 May 2026 15:18:44 +0000 https://dev.to/rishumishra/building-an-autonomous-vehicle-safety-test-framework-automating-misra-cert-c-compliance-3c9l https://dev.to/rishumishra/building-an-autonomous-vehicle-safety-test-framework-automating-misra-cert-c-compliance-3c9l <p>I built this to understand how autonomous vehicle teams validate safety-critical decisions against regulatory standards like MISRA C:2012, CERT C, and ISO 26262.</p> <p>Most AV test frameworks focus on functional behavior ("does it stop?"), but compliance validation — mapping each decision to specific safety rules — seems to be done manually. This framework automates that.</p> <p>Key features:</p> <ul> <li>AI-biased scenario generation weighted toward edge cases (30% fog vs 20% uniform, 40% critical severity)</li> <li>Validates AV decisions against ISO 26262 ASIL-D timing requirements (&lt;150ms for critical scenarios)</li> <li>Tests cybersecurity attacks (GPS spoofing, replay attacks, signal jamming) via Playwright API calls</li> <li>Generates compliance audit reports mapping each violation to specific MISRA/CERT rules</li> </ul> <p>Tech: Python (scenario gen), Java 17 + Playwright (API testing), JUnit 5 (compliance validation)</p> <p>The mock decision engine has 3 intentional bugs — the tests catch 2 of them (replay attack detection, ASIL-D timing violations).</p> <p>Built this as a learning exercise after 13 years in QA automation. Curious what folks working on real AV validation think I'm missing.</p> <p>GitHub: <a href="https://github.com/codingbuddha123/av-test-framework" rel="noopener noreferrer">https://github.com/codingbuddha123/av-test-framework</a></p> nvidia autonomous testing safety