You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
CLI calls to CLI REST client calls to REST API calls into code.
Mocking out the REST API to ensure that the CLI is calling the correct endpoints would be a useful sanity check.
Currently CLI + CLI REST client adds ~3 lines of uncovered "code" for every endpoint which brings down the reported code coverage of functional code.
Is there an easy way to test Click commands in situ?
Or: Move CLI client into its own repository?
The text was updated successfully, but these errors were encountered:
Mocking out the REST API to ensure that the CLI is calling the correct endpoints would be a useful sanity check.
that is effectively done in #441 , we could close this as redundant
CLI calls to CLI REST client calls to REST API calls into code.
Mocking out the REST API to ensure that the CLI is calling the correct endpoints would be a useful sanity check.
Currently CLI + CLI REST client adds ~3 lines of uncovered "code" for every endpoint which brings down the reported code coverage of functional code.
Is there an easy way to test Click commands in situ?
Or: Move CLI client into its own repository?
The text was updated successfully, but these errors were encountered: