QA and Test Engineering
Test strategy, validation frameworks, requirements traceability, and CI/CD quality gates for embedded and EV charging software.
Testing Capabilities
Testing Tooling Stack
| Category | Tools |
|---|---|
| Unit Testing (Embedded C) | Ceedling (core differentiator) |
| Unit Testing (C++) | GoogleTest |
| Functional Testing (Python) | pytest |
| Static Analysis | SonarQube, CodeRabbit, Linters, Pylint |
| Test Management | Jira, Polarion |
| Requirements Traceability | Polarion, Confluence |
| OCPP Conformance | OCTT-aligned (planned, availability dependent) |
| Coding Standards Verification | MISRA C |
Requirements Engineering
Clear requirements are the foundation of testable systems. Clemios provides requirements engineering as an integrated capability within the QA and test services. Requirements are captured, structured, and traced from stakeholder needs through to test verification.
- Requirements capture and structuring (Confluence, Polarion, Yogi)
- Traceability matrices linking requirements to test cases
- Change impact analysis and version management
- Compliance-ready documentation for automotive and industrial standards
OCPP Conformance Testing
Clemios is aligned with the Open Charge Alliance Testing Tool (OCTT) for OCPP conformance validation. OCTT testing is planned and will be integrated as the tool becomes available for the target OCPP profiles. The Clemios testing methodology already follows the validation patterns that OCTT formalises.
Related Services
Frequently Asked Questions
Clemios performs unit testing (Ceedling, GoogleTest, pytest), interoperability testing, regression testing, conformance testing, and CI/CD quality gate integration. The scope also includes test strategy, test case design, and test management.
Yes. Requirements engineering is integrated into the Clemios QA and test services. Clemios captures requirements, builds traceability matrices, and links requirements to test results using tools like Confluence, Polarion, and Yogi.
Clemios is actively testing with OCTT. The testing methodology follows the validation patterns that OCTT formalises. Formal OCTT status is not claimed.
Ceedling is a TDD framework for embedded C. Clemios writes unit tests before implementation, catching defects at the earliest stage. Most embedded vendors do not unit test firmware at all.
Yes. Clemios integrates test automation into existing pipelines (GitHub Actions, GitLab CI, Azure DevOps) and configures quality gates that prevent regressions.
Yes. Clemios uses Jira and Polarion for test management, with full traceability from requirements through test execution to results reporting.
Test Engineers for Embedded and eMobility
From Ceedling TDD to OCPP interoperability testing, from requirements traceability to CI/CD quality gates: Clemios test engineers deliver quality at every layer.