Add Tests for getting and setting component settings

[CryZe]

In #449 we accidentally merged too early. The component settings were in an inconsistent order. We can write a test per component that just iterates through all the settings and sets them with the value they already have. That way we have a basic "smoke test" that ensures that at least a basic interaction like that works across the board. That would've caught this.