Proper testing "apparatus" for the webapp and robot

[tejashah88]

One of the nuances with how the webapp is structured is that you need access to the hardware in order to fully ensure that all functionality works as expected. This is inconvenient when having multiple people work on hardware-dependent features, such as the sensor charts page or autonomous mode.

A possible solution would be to make a fake robot that simulates the sensor readings and allows developers to interact with it, as if it were the real thing. For now, it would be a virtual robot that's connected via websockets and spews out random data, except for the GPS.

[2bndy5]

As it is now works for anyone that freshly cloned the repo. config.json got renamed to HWconfig.json and then added to gitignore. Then HWconfig.json got renamed to HWconfig_template.json as a backup in order for the webapp to skip the hardware check. If they want to actually develop software for the hardware, they have to cp /inputs/HWconfig_template.json /inputs/HWconfig.json to enable the hardware check and then disabling certain hardware (unavailable during development) by prefixing the hardware's "driver" in the new copied json file with any character (s). I'm thinking it would be easier to stay a repo that's like a fork of the webapp, but minus all the GUI stuff...