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
Currently I'm testing new versions by manually running each of the examples against production services (Twitter, Google, GitHub, Meetup, and Spotify). But this requires credentials for each of these services, which I can't commit or use for CI.
One thing that we could do is script this to automatically call each of these services, but that still requires manual participation and can't be run in CI.
A possibly better approach would be to run a small mock server locally and authenticate against that. This wouldn't protect us against changes to the services we call (though they shouldn't be changing) but it would have caught some problems I had when upgrading to Swift NIO 2.0. The server could be built with the same TinyHTTPServer that we are using in the BrowserTokenProviders.
Currently I'm testing new versions by manually running each of the examples against production services (Twitter, Google, GitHub, Meetup, and Spotify). But this requires credentials for each of these services, which I can't commit or use for CI.
One thing that we could do is script this to automatically call each of these services, but that still requires manual participation and can't be run in CI.
A possibly better approach would be to run a small mock server locally and authenticate against that. This wouldn't protect us against changes to the services we call (though they shouldn't be changing) but it would have caught some problems I had when upgrading to Swift NIO 2.0. The server could be built with the same TinyHTTPServer that we are using in the BrowserTokenProviders.