Test suite for computations

[hvgazula]

(Partially) Akin to unit testing, I recommend maintaining a set of inputspecs with a corresponding small dataset for each to test the computation on before pushing the code for production. If there are concerns with storing data publicly, we could at least simulate an inputspec on open datasets. This suite approach will partially offset the lack of good (unit) tests for the computation code, thus ensuring code robustness.

@rssk @spanta28

[hvgazula]

Adding this feature will entail deleting the 'output' folder at the start of a test, so outputs from different tests don't clutter up. And since this is only for the simulator, I think this should be okay.