Eclipse openDuT provides an Open framework to automate the testing and validation process for automotive software and applications.
Eclipse openDuT developed as FOSS, to be transparent, open and trustworthy. It covers different test and validation domains. Most notable domains are security testing (penetration and fuzz testing), requirement testing, and smoke testing.
Eclipse openDuT considers an eventually distributed network of real (HIL) and virtual devices (SIL) under test. The actual devices under test are considered gray boxes, i.e., tests focusing on device-internal artefacts (e.g., software code or configuration) will not be in scope. Regarding the communication protocols, Eclipse openDuT puts its focus on the automotive protocols and considers external interfaces, protocols, components like WiFi, BLE, Charging Station and Mobile-Apps as relevant.
Eclipse openDuT reflects hardware capabilities and constraints along with the chosen test method (possibly in a predefined language – existing approaches will be evaluated). Test cases are not limited to a specific domain, but it especially realizes functional and explorative security tests. An example can be the execution of a functional test case where the correct update of a cryptographic key within an ECU, equipped with a security module, in context of Secure Onboard Communication is being verified.
Eclipse openDuT is hardware-agnostic with respect to the execution environment and accompanies different hardware interfaces and standards regarding the usability of the framework. Thereby, it is supporting both on-premise installations and hosting in a cloud infrastructure. Our framework shall be open to proprietary software (e.g., well-known tool chains and V&V tools) via tool-agnostic standardized interfaces and other established automotive architectures and standards (e.g. AUTOSAR). Eclipse openDuT aims on an OSS solution for automated testing and not on bridging different tool chains. One working stream within this project will deal with the comparison and interoperability with already existing OSS automotive V&V solutions to assure a broad acceptance by its users.
| Repo | Commits | Reviews | Issues |
|---|---|---|---|
| https://github.com/eclipse-opendut/opendut | 593 | 10 | 63 |
| https://github.com/eclipse-opendut/raspberry-pi-wireless-bootstrap | 8 | 0 | 0 |
| https://github.com/eclipse-opendut/.eclipsefdn | 4 | 1 | 0 |
| https://github.com/eclipse-opendut/netbird-build | 2 | 0 | 0 |
| https://github.com/eclipse-opendut/cannelloni-build | 2 | 0 | 1 |
There have been 609 commits made by 7 people on 5 repositories over the last 12 months.
There have been 64 issues submitted by 9 people on 2 repositories over the last 12 months.
There have been 11 reviews submitted by 3 people on 2 repositories over the last 12 months.
The EMO oversees the lifecycle of Eclipse projects, trademark and IP management, and provides a governance framework and recommendations on open source best practices.
See the project’s PMI page at https://projects.eclipse.org/projects/automotive.opendut
TruereadThis project has a total of 7 repositories in its associated GitHub organization eclipse-opendut
.
The graph below outlines the percentange of repositories that have either defined a Branch Protection Rule or Repository Ruleset:
SDV Maturity badges recognise achievements made by the project towards the SDV maturity assessment goals. Learn more on the dedicated page .
These badges only apply to the SDV Working Group .
Warning
This page is under construction
We are currently working on a definition and prototype for SDV badges, please see the SDV Process .
Is the project used to showcase the resolution of a real-life situation, either individually or integrated with other Eclipse SDV projects? See the SDV Blueprints project for more information.
This project has not registered any activity on the criteria.
How well is the project doing when it comes to Requirements e.g. defining, versioning and managing, traceability, coverage, etc? For more details on the needs for the different levels of the Requirements Criteria read its definition here .
This project has not registered any activity on the criteria.
How well is the project doing when it comes to Testing e.g. defining, versioning and managing, traceability, coverage, types of tests etc? For more details on the needs for the different levels of the Testing Criteria read its definition here .
This project has not registered any activity on the criteria.
How well is the project doing when it comes to Documentation e.g. types of documents depending on contents, versioning, etc? For more details on the needs for the different levels of the Documentation Criteria read its definition here .
This project has not registered any activity on the criteria.
How well is the project doing when it comes to Coding Guidelines e.g. defining, adhering, managing issues etc? For more details on the needs for the different levels of the Coding Guidelines Criteria read its definition here .
This project has not registered any activity on the criteria.
How well is the project doing when it comes to Releases e.g. defining a process, versioning and managing, release notes, coverage etc? For more details on the needs for the different levels of the Release Process Criteria read its definition here .
This project has not registered any activity on the criteria.
Is the project respecting OSS good practices files in their repositories? See also the legal documentation checker for more information.
<a href="https://metrics.eclipse.org/projects/automotive.opendut" alt="OSS Best Practices badge for automotive.opendut"></a>
Repo .github has some of the recommended files.
Found categories: SECURITY, README
Repo cannelloni-build has some of the recommended files.
Found categories: README, LICENSE, AUTOMATION
Repo netbird-build has some of the recommended files.
Found categories: README, AUTOMATION
Repo netbird-fork has some of the recommended files.
Found categories: AUTOMATION, CONTRIBUTING, SECURITY, LICENSE, README, CONDUCT
Repo opendut has some of the recommended files.
Found categories: BUILD, LICENSE, AUTOMATION, README, CONTRIBUTING, CONDUCT
Repo raspberry-pi-wireless-bootstrap has some of the recommended files.
Found categories: LICENSE, BUILD, README
Repo rperf-build has some of the recommended files.
Found categories: README