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
{{ message }}
This repository was archived by the owner on Aug 30, 2024. It is now read-only.
As coder-cli runs against the backend (cdr/enterprise) and depends on its APIs, it would make sense to do some tests of the coder-cli tool itself as part of the main integration checks.
Major features could be tested to ensure they still function, eg:
sync
sh
devurls
add
update
list
delete
The text was updated successfully, but these errors were encountered:
Russtopia
changed the title
Integration tests for coder-cli on enterprise CI pipeline
Integration tests for coder-cli
Jun 29, 2020
We'll test changes as the API changes, so we can catch API breaks as a part of the PR in enterprise, instead of tests randomly break in here
We'll be able to re-use the data scaffolding code for frontend e2e tests, so that you can independently test each method instead of having to test CRUD as one whole flow
Closing as the coder-cli work is done. The remaining phases involve configuring enterprise namespace deployments and pointing the integrations tests towards mocked APIs.
As coder-cli runs against the backend (cdr/enterprise) and depends on its APIs, it would make sense to do some tests of the coder-cli tool itself as part of the main integration checks.
Major features could be tested to ensure they still function, eg:
The text was updated successfully, but these errors were encountered: