Integration tests

[dentarg]

Dedicate an auth0 account for tests, keys can be encrypted in .travis.yml, write tests that actually do stuff with the API.

What do you think?

[jfromaniello]

Yes, it make sense @hzalaz will look into this.. thank for all your feedback

[dentarg]

@hzalaz I noticed 6e19b8f

When 2 builds run in parallel, they clash with each other.

I think the answer is https://github.com/vcr/vcr

GitHub uses it for their API client, you can read about it at https://github.com/octokit/octokit.rb#running-and-writing-new-tests

[dentarg]

I think the answer is https://github.com/vcr/vcr

...not to remove number of Ruby versions to test against

[hzalaz]

I know about vcr but in my experience the recorded tests will get outdated easily and everything will seem ok when it shouldn't, that's the reason I'd rather hit the API directly for integration tests. Also we're already mocking http in unit tests (I'd rather use them there) so both test will be exactly the same.

I want to rework the "new tests" to avoid clashing with each other (like prefixing ids) but until then I prefer a reliable build.

[dentarg]

I understand. Nice work on this!

[hzalaz]

We don't have all endpoints tested against the real API but at least we have most of /users which should be the most used. We'll continue to add more endpoints eventually. PR are welcome! 😄