Create a local server for testing of netsender
Issue #25
new
The unit tests of netsender communicate with the net-receiver server. This is an issue because the testing device has been removed from the netreceiver website. It would be nice to have a local server that is run inside the test routines because then the tests are not affected by external changes.
Comments (5)
-
-
We can’t use Vidgrind in standalone mode on CI though right ? Would it make sense to have two tests; one could use a standalone instance of vidgrind and the other could use a really dumb server ? We would skip the vidgrind test on CI and just use the dumb server test, but on a local machine we can run both.
-
There is no reason why a test instance of VidGrind could not run on CircleCI, either in standalone more or App Engine mode (depending on what the test is trying to achieve). Rather than proliferating test services (such as “NetSpoofer” which become maintenance headaches), it is better to build testability into our production services. If VidGrind is missing functionality required for testability, then let’s address that.
-
reporter
I will look into that
-
Tests are now passing again with https://bitbucket.org/ausocean/iot/commits/5758d245e5e9f433b631e44a61fb259bc4f8f160
- Log in to comment
There is no need for a special local server, since VidGrind can be used in standalone mode (which automatically creates a test site, test device and test user). Please read https://docs.google.com/document/d/1W_N_3VRHmG7AEHdPfV05eMGcAFpzQJc1ghpuZuQQfeg/edit
Also, there is still a NetReceiver test site (site key 1) for online testing, but tests are required to create (or re-create) the test device as needed.