Ensuring Requirements on the SEAPATH Project: Testing Process and Continuous Integration
summary
SEAPATH (CPAS) builds a software-centric substation using a real‑time Linux kernel, KVM/QEMU, Open vSwitch (DPDK optional), Yocto and Debian images, and publishes a software bill of material via SPDX. CI runs on a dedicated cluster via GitHub Actions, Ansible and SonarQube, producing PDF test reports per pull request. The repo shows 1800 commits and about 700 tests covering unit VM startups, ANSSI BP28 security checks and IEC 61850 latency; Yocto CI is newly enabled and robustness failure-injection tests are pending.
AI-written summary · about
chapters (5)
- 0:00Introduction and project overview
- 2:48CPAs project goals and requirements
- 8:27Testing scenarios and compliance
- 13:51CI implementation and workflow
- 19:19Q&A session
related talks
32mSEAPATH: What's New - Recent Improvements and Future Developments
26mWhat Do Virtualization and SEAPATH Really Change for RTE ?
32mTesting the Resilience of a SEAPATH Cluster: In Search of Single Points of Failure
27mPre-Packaging CRA and NIS2 Compliance: The SEAPATH Approach
23mA Case Study on Testing LFE Seapath at National Grid Electricity Transmission
25mBad Behaviour: Automating System-level Safety Testing Using Open Source Tools
37mAutomated Testing and Continuous Integration/Delivery: Lessons Learned
33mOpenStack Compute's automated testing