trying to run tests as a developer... about xeroizer

[timdiggins]

Actually - I've worked that one out - there was a line in tax_rate_test.rb which really needs to be in unit_test_helper. See PR

[rjaus]

Personally, I use Insomnia Rest client to run the authorisation, then I export my access token & tenantId into my local environment
export XERO_ACCESS_TOKEN=asdfsadfsafsdf
export XERO_TENANT_ID=asdfasdf

I guess this could be resolved by writing some setup tests which throw open a browser to conduct the oauth flow, to save the token & tenantId in the test environment.

The demo company needs to be manually reset, which is an additional complication for running automated tests.

[timdiggins]

Thanks Riley. What do you think about adding vcr to the test setup and making the setup and (re)generation of the vcr cassettes a manual occasional process for developers?

However maybe given that xero are behind https://github.com/XeroAPI/xero-ruby maybe it's more sensible for me to focus efforts on switching to that gem rather than pouring effort into this one.

[rjaus]

Hey @timdiggins, if you are at an early enough stage that switching is possible, then moving to xero-ruby would make sense. Xero will definitely be focusing its efforts on that SDK. Xeroizer has always been a community led effort.

But where ever you choose to throw PRs, we definitely appreciate them! 👍

[timdiggins]

@rjaus Thanks, helpful. Could you merge #550? It's a good and (I think) uncontroversial fix for a misplaced require which is not related to #551