Test coverage

[naorlivne]

there really should be unit tests, the project is scaling to a level of complexity it's getting too hard to keep track otherwise... thinking TrevisCI (or equivalent) tool that will build a Nebula stack to make sure noting major breaks the project to a level it's unusable as a starting point then slowly adding unit tests until the test coverage reaches ~100% then afterwards setting a requirement\procedures for new changes to be only accepted with unit tests... likely a very long term goal but still an important one to set.