jordanhudgens / analytics Goto Github PK

That's the final piece of the puzzle. You can test this as a /test URL in your tracking app, as discussed before.

JavaScript snippet should replace the token in views, so some previous tests will need updating to reflect this.

First make sure the database has its own set of comprehensive unit tests. Each method should be tested.

Choose the database engine to be used, then a ruby driver and finally replace Database class code with one using the DB driver.

Potentially also add rake tasks for initializing the database, if needed.

After tracking traffic (i.e. getting /request with the token), user should be able to see a rudimentary statistics for her site (e.g. total number of events, or ordered by date in a table).

Each user should have a unique token (write a test for this as well: register two users and make sure each has a different token).

Sample test cases:

• Request API should store data in account-specific collections based on the passed token.
• Request API should return HTTP 403 error code when token is unknown.
• Request API should return HTTP 404 when called with the wrong HTTP verb (i.e. not POST but GET).

After registering, user should be able to see the token.

Deploy the analytics app to Heroku and add the JavaScript snippet to the Bloccit app. Manually test it: make sure you can register an account and that statistics for Bloccit are coming through.