e2e-tests: authd-google browser login is blocked by CAPTCHA
- Dominant language
- Go
- Stars
- 308
- Forks
- 41
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 58
Description
The E2E tests that use the `authd-google` broker are consistently failing because Google now displays a CAPTCHA during every browser login attempt.
The browser automation cannot complete the CAPTCHA, so the Google login flow cannot finish and the tests fail.
All runs are affected. [Here](https://authd-e2e-test-logs.adrian-dombeck.workers.dev/pr-1869/run-33817478961-1/resolute-authd-google/log.html#s1-s1) is one example.
Contributor guide
Research direction
Start with the E2E tests using the authd-google broker and inspect the linked failing run log to trace where browser login stops. Determine a supported way for the affected tests to complete despite the CAPTCHA; done means the Google login flow finishes and all affected E2E runs pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- authentication, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100