The recent PR #443 did a bit of cleanup by removing the empty module transportConfiguration in executables/unitTest.
The actual idea would be to unify the transportConfiguration for all unit tests similar as e.g. lwipConfiguration or udsConfiguration.
The task would be to re-create the module transportConfiguration in executables/unitTest and unify all TransportConfiguration.h files which are used for unit tests and move it to this one module.
The rational is this: Having each unit test self-contained (it brings all dependencies with it) leads many copies of the same file, e.g. TransportConfiguration.h many of them being very similar. When we then do an actual change, all of these files need to be updated. The unifying approach provides a little less flexibility and can still be used if no other solution is possible (e.g. for a specific unit test with a different configuration) but the approach of having one common unit test platform/configuration increases maintainability.
The recent PR #443 did a bit of cleanup by removing the empty module
transportConfigurationinexecutables/unitTest.The actual idea would be to unify the
transportConfigurationfor all unit tests similar as e.g.lwipConfigurationorudsConfiguration.The task would be to re-create the module
transportConfigurationinexecutables/unitTestand unify allTransportConfiguration.hfiles which are used for unit tests and move it to this one module.The rational is this: Having each unit test self-contained (it brings all dependencies with it) leads many copies of the same file, e.g.
TransportConfiguration.hmany of them being very similar. When we then do an actual change, all of these files need to be updated. The unifying approach provides a little less flexibility and can still be used if no other solution is possible (e.g. for a specific unit test with a different configuration) but the approach of having one common unit test platform/configuration increases maintainability.