Fabian Greif

> It is then be convention that these both containers should never ever be connected to the same network at the same time. With this convention it would be possible...

> A component can be secondary/passive to as many containers as the user wishes. > Typically, these are instances for simulation and debugging, e.g. on non-microcontroller hardware. That sounds strange...

> Is there a strategy to split the unittest into smaller chunks which can be tested individually? Well, the typical way would be to group the test into test suites...

That is true. The solution I had in mind would actually not bring any speed-up (or only if we're IO write limited), but would instead allow to detect local changes...