Reviews run for a minimum of one week. The outcome of the review is decided on this date. This is the last day to make comments or ask questions about this review.
Eclipse Kiso-testing
Embedded software as a field is continuously evolving. More powerful CPUs (e.g., ARM Cortex M) and communication possibilities (e.g., LoRa, NB-IoT, ...) are allowing us to create new kind of devices (e.g., IoT (INTERNET OF THINGS) field) with a new kind of complexity.
Harnessing this complexity is a key to build great products. To do so, embedded developers need to be able to test (automatically) if each contribution they are doing works with the current software.
By scouting the open-source landscape, it was not possible to find a tool or framework that allowed to test every aspect of embedded software for a developer.
The Eclipse Kiso-testing project provides an integration test framework for embedded software.
With Eclipse Kiso-testing it is possible to write:
-
Whitebox integration tests directly on the arget device
-
Graybox integration tests to make sure the communication-link with the target device is working as expected
-
Blackbox integration tests to make sure an external device interfaces are working as expected
The project will contain:
-
The core python framework (creates the testing environment and run the tests)
-
Plugins for the core framework (functionalities that can be used for creating the testing environment and used by the running tests)
-
Additional libraries for different target platforms (e.g., stm32, ...) or languages (C, C++, ...) that enable you to deploy tests on different targets.
With the Kiso-testing platform it is possible to write tests by directly
-
Using python unittest native like test-cases
-
Using the robot-framework keyword-based test-cases
The Kiso-testing tool provides the needed functionalities to generate the following reports:
-
Junit reports
-
Requirement coverage reports
-
Robot framework reports
Eclipse Kiso (https://github.com/eclipse/kiso) is/was hosted by the Eclipse foundation. Kiso-testing was a sub-project. It became more popular than the initial project as such.
This project proposal is about transforming an Eclipse foundation sub-project to a standalone one.
The code is already open-sourced
The code was already developed as EPL-2.0 License license. Internal clearance was already handled. Users already signed the ECA.
I will request a scan from your side very soon.
Everything should already be open-sourced.
We will continue to work and contribute to Kiso-testing until it gets changed to a main Eclipse project.
We do not have a roadmap as such, the main development happened the past 2 years. We do have internal customer requesting features (on two weeks base) and plan internally to grow the number of customers/users.
Next steps would be to increase, also externally, awareness about the project. To do so, we will participate to the EclipseCon and other open-source events.