The current integration tests (which use a live HVCA account) need revision. Currently:
They are tied specifically to my personal HVCA demo account. Really we should create one or more HVCA demo accounts specifically for use with testing this client
Some of them rely on specific text in HVCA error messages, which is not documented, and causes and has caused test failures when that error text changes. It is probably not necessary to validate the error message text, and the tests ought to be revised to not do that
Some of the tests are probably not necessary. For example, the tests for the /stats endpoints validates that we do indeed get some kind of "page size too large" error when we supply a large page size. This was useful during development to confirm everything was working as it should and to confirm my understanding of what HVCA was doing, but realistically this is testing HVCA operation more than it's testing the operation of the client, so it's probably not necessary here.
If we want to be able to run these integration tests from the Github build, we'll need to add the relevant credentials as secrets for this repository.
The current integration tests (which use a live HVCA account) need revision. Currently:
If we want to be able to run these integration tests from the Github build, we'll need to add the relevant credentials as secrets for this repository.