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 has been archived by the owner on Nov 27, 2018. It is now read-only.
We need to figure out how to test the configure command. I confess to having no good idea how to do this.
The command depends on the GitHub and Travis APIs, so perhaps we could stub those.
Or I guess we could create a GitHub user specifically for testing, then encrypt that user's username and password for Travis. That still wouldn't allow us to test 2FA, nor perhaps some other aspects of the configuration flow, but it could test many aspects. However, it would be a live test, dependent on the status of the GitHub and Travis API endpoints.
The text was updated successfully, but these errors were encountered:
We need to figure out how to test the configure command. I confess to having no good idea how to do this.
The command depends on the GitHub and Travis APIs, so perhaps we could stub those.
Or I guess we could create a GitHub user specifically for testing, then encrypt that user's username and password for Travis. That still wouldn't allow us to test 2FA, nor perhaps some other aspects of the configuration flow, but it could test many aspects. However, it would be a live test, dependent on the status of the GitHub and Travis API endpoints.
The text was updated successfully, but these errors were encountered: