Added Travis-CI integration in the API. Now at each commit I make on github, Travis will test the API by running the
test.py file, and will inform if the build fails.
In the API, when a user sends the data with same
unique_user_id, i.e another attempt, API was not updating the
UserSystemInfo on this request, assuming the system’s information will remain same even in the second request. But this isn’t true for
workshop_id. A user may enter the email id in the second attempt, while may have denied in the previous one. And also, they may have entered a wrong email id in the previous attempt, so they might want to update them in the next. So everytime a user makes a request, system’s information is also updated.
But this may create a problem. If second time user doesn’t enter the email and workshop id, the API will rewrite the email and workshop field to
None. So API should update only when the received email or workshop id is not
None. Added the unit test for the same.
Tested the scripts at various platform of linux and windows as well. But I had no access to OS X. So Piotr Banaszkiewicz asked Greg Wilson to test the scripts on his OS X machine and share the feedback with us. The scripts ran without any issues on OS X as well.
I have increased the rate limit to 500 per hour per IP for the time. As when I was testing the API on my computer, the test script made more than 10 calls to API on single execution, and thus very soon all the tests started failing, as the limit had reached.
Now, I think it’s time to get going with the frontend, and visualize the data with charts and statistics. There are several options like Plotly.js, C3.js, MetricGRaphics.js etc. I’ll select the most approriate library after having all the use cases with me. MetricGraphics is a well maintained JS library by Mozilla. But it seems like more for timeline purpose. So I may have to rely either on Plotly or C3. They kinda do justice to my requirements. Anyway, I’ll come to that later.