Use of VCR.py to not depend on an Odoo server and speed up tests

[sebalix]

Like it is done on OCA/connector-magento.
Link: VCR.py

[pedrobaeza]

We have the same also on connector-prestashop, but with that, we are faking the possible problems IMO.

[sebalix]

My idea is to put the resulting serialization of HTTP queries in Travis cache (expiration every 28 days: https://docs.travis-ci.com/user/caching/#caches-expiration). I know some issues may be hidden this way if Odoo changes its internals, but currently tests are also very slow (+ Travis jobs are shared among all OCA reporitories).

[pedrobaeza]

@guewen what is your experience using VCR?

[guewen]

@guewen what is your experience using VCR?

It depends on what needs to be tested:

• It's a blessing for unittest and refactoring your code, when the "other side" doesn't change, as you can run your "red-green-refactor" loop very fast and generally ensure you don't break existing features
• Consequently, in a dev workflow, it makes the dev way faster because you don't have to rollback the changes on the "other side" when you want to retry an operation, you can run it on the registered responses
• It does not replace real integration tests with a service (but it's still a weak replacement which doesn't need complex test setup)

In any case, IMO it's already worth it for the point 1 alone.