iterative
Separate unit tests from acceptance tests
CML is a project that relies heavily on external infrastructure, and some acceptance tests are practically unavoidable if we want to make sure that nothing breaks. Nevertheless, I was wondering if we could mock as much as possible to separate unit from acceptance tests, enabling users to check their contributions for errors without having to care about those services.
Solving this would probably imply repourposing ~test.yml~ deploy-test.yml from ~#526~ #530 to run unit tests first and relying on GitHub Environments just for acceptance tests.
Tensorboard tests are flaky because of rate limits: yet another reason to separate unit tests from acceptance tests and only run the latter on demand.
I don't find a proper way to do such unit tests aside recording the API responses as I have said so many times. If you are willing to do so @0x2b3bfa0 you have to setup sinon.js to mock the real responses.
