You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The application has already been equipped with the correct testing tools. Now the entire codebase should be furnished with tests in order to keep the code reliable and stable.
I have to wait until iced 0.14 to use it. The CLI version as well as the entire lib can be tested already. The testing of the GUI gets separated into its own ticket dependant on iced 0.14. Work on that can already begin on a loose branch using the GIT-version of the iced dependency.
every file contains a test for the corresponding file contents
those tests split in unit tests for detailed logic testing and integration tests for the interaction of functions
a separate tests folder contains integration tests, that run directly on a simulated CLI. Those tests are completely separated from the production code, because they alter the environment.
In #109 the preparation for the testing of the lib was done — a refactoring regarding the lib.rs. most parts of that integral part of the software is already tested by now, a PR will probably follow tomorrow.
How many tests GUI, CLI and usbio get, will be decided tomorrow as well. But it's on its way ;)
Activity
Hirschfuchs commentedon Nov 24, 2025
The testing framework for iced is currently under construction: https://github.com/iced-rs/iced/tree/190b9f60b4b189767ca5d71eb82d8954ac4a55cd/test
I have to wait until iced 0.14 to use it. The CLI version as well as the entire lib can be tested already. The testing of the GUI gets separated into its own ticket dependant on iced 0.14. Work on that can already begin on a loose branch using the GIT-version of the iced dependency.
Hirschfuchs commentedon Nov 24, 2025
As of now, I separated the tests:
testsfolder contains integration tests, that run directly on a simulated CLI. Those tests are completely separated from the production code, because they alter the environment.➕ #106: Added mocking framework mockall
➕ #106: Added cmd testing framework assert_cmd
✅ #106: Test for the decoding of the CameraStatus
🚧 #106: Preparation: Separated testing of the CLI
🚧 #106: First playing around with cli tests
Hirschfuchs commentedon Nov 25, 2025
In #109 the preparation for the testing of the lib was done — a refactoring regarding the lib.rs. most parts of that integral part of the software is already tested by now, a PR will probably follow tomorrow.
How many tests GUI, CLI and usbio get, will be decided tomorrow as well. But it's on its way ;)
➕ #106: Added mocking framework mockall
19 remaining items
✅ #106: Added tests for Enum Displays
✅ #106: Added tests for Command02
✅ #106: Added tests for the commands
🧑💻 #106: Defined folder for integration tests
✅ #106: Added tests for the commands
🧑💻 #106: Defined folder for integration tests
➕ #106: Added "testcase" for parameterized tests
✅ #106: Added tests for CameraStatus
✅ #106: Added tests for Enum Displays
✅ #106: Added tests for Command02
✅ #106: Added tests for the commands
🧑💻 #106: Defined folder for integration tests
Hirschfuchs commentedon Dec 5, 2025
The basic unit tests have been integrated. All other work was separated on branches and will be continued under #119