Skip to content

tests: Add basic "successful/failed login" test cases #2067

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.

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

Merged
merged 3 commits into from
Dec 28, 2019

Conversation

Turbo87
Copy link
Member

@Turbo87 Turbo87 commented Dec 26, 2019

This PR adds two basic application tests for the login button and the login route. Please note that this does not test the github-login and github-authorize routes yet, which we will do in a follow-up PR.

r? @locks

/cc @carols10cents

@locks
Copy link
Contributor

locks commented Dec 28, 2019

@bors r+

@bors
Copy link
Contributor

bors commented Dec 28, 2019

📌 Commit f9007c1 has been approved by locks

@bors
Copy link
Contributor

bors commented Dec 28, 2019

⌛ Testing commit f9007c1 with merge 498506f...

bors added a commit that referenced this pull request Dec 28, 2019
tests: Add basic "successful/failed login" test cases

This PR adds two basic application tests for the login button and the `login` route. Please note that this does not test the `github-login` and `github-authorize` routes yet, which we will do in a follow-up PR.

r? @locks

/cc @carols10cents
@bors
Copy link
Contributor

bors commented Dec 28, 2019

☀️ Test successful - checks-travis
Approved by: locks
Pushing 498506f to master...

@bors bors merged commit f9007c1 into rust-lang:master Dec 28, 2019
@carols10cents
Copy link
Member

Catching up on what's been merged, this is awesome!!! Thank you so much!!!

@Turbo87 Turbo87 deleted the login-tests branch January 2, 2020 19:25
@smarnach
Copy link
Contributor

smarnach commented Jan 2, 2020

Yup, this is one of the tests that were most sorely missing from the frontend. Actually, the first time I tried to set up crates.io on my machine the login was broken, and it took me a while to figure out what's wrong since the error output goes to the ephemeral new window, and all tests pass. These tests would have caught the error with an easily accessible error message, and the broken change would have been fixed within minutes before it was even merged.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants