udacityalumni / udacity-alumni-api Goto Github PK

@RyanCCollins has assigned me the task of running rspec tests on all PR repos as they come in in order to make sure all the tests are passing. I was wandering how others usually approach testing when working on other projects. Do you follow TDD practices, not write any tests at all, or somewhere in between?

We have talked and decided it would be a good idea to add a profile model, along with a One to Many related model for tracking user's nanodegree enrollments.

I believe we are going to want to build a commenting system to make the site more interactive. Will be talking with David about this today.

We want to have full documentation coverage of our REST API, models, etc.

Note: a session and user controller was created that is working, but not yet tested.

Just noticed that some of the boilerplate tests were left in. Would love some help getting the tests to pass for the articles controller. Thank you!

Do we want to have multiple sign ins? How do we handle having multiple valid tokens? Should we send a 401 that logs the user out?

It might be a good idea to add a namespace to the api, so that we can do something like: /api/v1/articles vs. just /articles. I can take a stab at it, but wanted to let people know.