Implement unit tests for core features
To extend MR !71 (merged) unit tests for core library functionality should be added.
@kwolters said in !71 (merged) :
Regarding the core tests, I think these can be added later as well. But anyway for all the components:
- Config: Here it would be best to convert strings to configurations using the ConfigReader and check that the format is parsed according to specifications (and an exception is thrown if not). Not critical as the most important features are already tested with the module configs.
- Modules: Just pass a variety of Configuration objects to the ModuleManager and check if the modules are instantiated as expected. Not critical as well as the most important features are also tested with the module configs.
- Messenger: Create two test modules and send messages between them. The tricky part here is that we also want to check that the messaging system is fully thread-safe.
- Geometry: This is probably the most critical thing to test. We have to make sure that all transformations and sizes remain correct (after we verified they are fine).
I can try to add some simple tests for the core if you want? Probably we should just use a simple unit test framework, First hit on google gave this, looks fine.
I do agree but wouldn't spend a large amount of time on this right now.