[core] Extend existing E2E tests
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 52/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- playwright, typescript
- Domain
- testing
Research direction
Start with the listed test cases in e2e/tests/rateLimit.spec.ts, e2e/tests/users.spec.ts, e2e/tests/aclBulkActions.spec.ts, and e2e/tests/gatewayAdoption.spec.ts; also inspect the edge-component setup reference in e2e/utils/globalSetup.ts. Run the existing E2E suite to learn its setup and conventions. Done means adding the eight specified UI flows and verifying each expected message, status, or outcome.
Written by the indexing model from the issue text.
Description
-
e2e/tests/rateLimit.spec.ts:79: add failed login via UI (wrong password + unknown username, check error message) -
e2e/tests/rateLimit.spec.ts:124: add wrong TOTP/email code on the MFA screen in UI (user not logged in) -
e2e/tests/users.spec.ts:91: add single user delete via "…" → "Delete account" (user can't log in afterwards) -
e2e/tests/aclBulkActions.spec.ts:175: add single alias delete via "…" → "Deletion blocked" modal, alias stays -
e2e/tests/aclBulkActions.spec.ts:252: same for destination ("Deletion blocked" modal) -
e2e/tests/aclBulkActions.spec.ts:83: add single rule disable/enable via "…" + deploy, check status "Disabled"/"Active" -
e2e/tests/gatewayAdoption.spec.ts:112: add gateway adoption via UI wizard (Gateway Name, IP, adoption steps, "Go to locations") -
e2e/utils/globalSetup.ts:113: add separate test for "Edge Components" → "Add Edge Component" wizard (confirmation, duplicate name error)
- Dominant language
- Rust
- Stars
- 2.9k
- Forks
- 119
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 61
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from DefGuard/defguard
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
All issues in DefGuard/defguard
Similar issues
-
good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
NuSkooler/enigma-bbs#907 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
bug pixi-build-r
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
prefix-dev/pixi#7229 ·
Maintainers usually reply within 1 day