Free SKILL.md scraped from GitHub. Clone the repo or copy the file directly into your Claude Code skills directory.
npx versuz@latest install hiyenwong-ai-collection-collection-skills-automated-cps-testing-actgit clone https://github.com/hiyenwong/ai_collection.gitcp ai_collection/SKILL.MD ~/.claude/skills/hiyenwong-ai-collection-collection-skills-automated-cps-testing-act/SKILL.md---
name: automated-cps-testing-act
description: "Automated CPS Testing Framework (ACT) for continuous testing of open-source cyber-physical systems with robotic platforms. End-to-end automated testing integrated with open-source infrastructure such as GitHub. Use for: continuous CPS testing, open-source robotic platforms testing, multi-module CPS validation, GitHub-integrated testing workflows. Activation: automated CPS testing, cyber-physical systems testing, robotic platforms testing, continuous CPS testing, ACT framework."
---
# Automated CPS Testing (ACT) Framework
End-to-end automated testing framework for cyber-physical systems (CPS) with robotic platforms, integrated with open-source infrastructure.
## Overview
ACT addresses the gap in robust testing for open-source CPS software by providing:
- Automated continuous testing with robotic platforms
- Integration with open-source infrastructure (GitHub)
- Multi-module CPS testing support
- Detection of critical errors in distributed contributor environments
## Core Concepts
### Testing Challenges in Open-Source CPS
1. **Multi-Contributor Complexity**: Multiple modules developed by various contributors
2. **Hardware Integration**: Testing requires physical robotic platforms
3. **Continuous Validation**: Need for ongoing automated testing
4. **Infrastructure Integration**: Must work with existing open-source workflows
### ACT Framework Components
```
┌─────────────────────────────────────────┐
│ ACT Testing Framework │
├─────────────────────────────────────────┤
│ GitHub Integration Layer │
│ ├── CI/CD pipeline hooks │
│ ├── Pull request testing │
│ └── Issue tracking │
├─────────────────────────────────────────┤
│ Test Orchestration Layer │
│ ├── Test case generation │
│ ├── Platform abstraction │
│ └── Result aggregation │
├─────────────────────────────────────────┤
│ Robotic Platform Layer │
│ ├── Hardware interface │
│ ├── Safety monitoring │
│ └── Real-time execution │
└─────────────────────────────────────────┘
```
## Workflow
### 1. Setup Phase
```python
# Configure ACT for your CPS project
act_config = {
"platform": "educational_robot", # or custom platform
"github_repo": "org/cps-project",
"test_suite": "comprehensive",
"execution_mode": "continuous"
}
```
### 2. Test Execution
```python
# Run automated tests
test_results = act.run_tests(
modules=["control", "planning", "perception"],
scenarios=["normal", "edge_cases", "fault_injection"],
duration="automated"
)
```
### 3. Integration with GitHub
```yaml
# .github/workflows/act-testing.yml
name: ACT Testing
on: [push, pull_request]
jobs:
act-test:
runs-on: act-runner
steps:
- uses: actions/checkout@v3
- name: Run ACT Tests
run: act execute --platform robotic
```
## Implementation Guide
### Test Case Design
1. **Unit Tests**: Individual module validation
2. **Integration Tests**: Cross-module interactions
3. **Hardware-in-the-Loop**: Real robotic platform testing
4. **Scenario-Based**: Real-world use case validation
### Safety Considerations
- Hardware safety monitoring during automated tests
- Emergency stop mechanisms
- Gradual test complexity escalation
- Sandbox environments for new contributors
## Tools and Commands
| Tool | Purpose | Usage |
|------|---------|-------|
| `act init` | Initialize ACT for project | `act init --platform <type>` |
| `act run` | Execute test suite | `act run --suite <name>` |
| `act report` | Generate test reports | `act report --format html` |
| `act ci` | CI/CD integration | `act ci --github-repo <url>` |
## Activation Keywords
- automated CPS testing
- cyber-physical systems testing
- robotic platforms testing
- continuous CPS testing
- ACT framework
- open-source CPS validation
## Related Skills
- `systems-engineering`: General systems engineering patterns
- `control-systems`: Control theory and implementation
- `robotics`: Robotics-specific methodologies
- `ci-cd`: Continuous integration practices
## References
- Paper: arXiv:2604.11708 (April 2026)
- Authors: Krishnan, Kim, Kim
- Application: Educational robotic platforms
## Example Usage
```
"Set up ACT for my open-source robotics project"
"Configure continuous testing for CPS modules"
"Integrate robotic platform testing with GitHub Actions"
"Run automated tests on multi-contributor CPS software"
```
## Notes
- Designed for open-source projects with multiple contributors
- Requires physical robotic platform access
- Integrates seamlessly with GitHub workflows
- Supports educational and research robotic platforms