Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Create end to end tests for common providers #160

Closed
ib-lundgren opened this issue Nov 6, 2014 · 2 comments
Closed

Create end to end tests for common providers #160

ib-lundgren opened this issue Nov 6, 2014 · 2 comments

Comments

@ib-lundgren
Copy link
Member

These tests should be automated but could be excluded from the standard suite if there is no good way to hide real client ids and secrets in a test setup such as travis.

A good start would be for Google, Twitter and Facebook.

Ideally this should further help making new releases smoother. cc #157
@dasevilla
Copy link
Contributor

Some of the OAuth flows require user interaction (i.e. sign in with your Google account and approve). Would this be for the OAuth 2.0 client credentials grant?

@JonathanHuot
Copy link
Contributor

Closed as part of the 1.4.0 release #530
I'm suggesting to open a new MR for each "common providers" when working on it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@dasevilla @JonathanHuot @ib-lundgren