sillsdev / sillsdev/languageforge-lexbox

e2e test google login

Open
#607 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

📦 Lexbox Needs design testing
Dominant language
C#
Stars
9
Forks
8
Avg merge
2d 13h
Merged PRs (30d)
49

Description

There's some various guides online, some of them setup a gmail account and use that for testing the login, that seems problematic because google tries to block bots from their login page. If there's a better way let's do it, if that's the only way then I don't think it's worth the cost.

At the very least we should have a test that clicks the button and asserts that we land at a google login page, even if we don't verify that we make it all the way through.

It would be good to also test the registration process as part of the google login, but that could be even more difficult.

Article suggesting how to test, not sure how well it will work
https://docs.cypress.io/guides/end-to-end-testing/google-authentication

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the existing Google login button and the end-to-end test setup, then review the linked Cypress Google authentication guide. Done should include a test that clicks the button and asserts navigation to a Google login page; full registration coverage remains an optional, unresolved extension.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp, cypress
Domain
authentication, testing
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.