Fixing nutrition set parsing and schema bugs
Offline functional tests and necessary dummy APIs for the Shim
Better way to read the resulting data from the HTTP response from the API
I verified the nutrition data against the wrong actual data due to undocumented functionality of the Runkeeper API I happened to stumble upon. As it turns out Accept headers matter *a lot* and a typo in one can get you undocumented functional responses. These changes reverify the Nutrition data against the correct response from the API with the correct accept header.
A highly (my account) specific online functional test to test the actual API calls. This functional test is removed for the test target in the build script because it will fail unless setup correctly since the OAuth is done manually.