refac: hardening pass with multiple overhauls
This commit is contained in:
1 parent
b0f7b7892b
commit
da36c78bc0
28 files changed
+1375
-39
No files matched your search
@@ -132,10 +132,11 @@ Feature: An invited person accepts their invitation and gets a verified account
|
||||
Then the response status is 200
|
||||
And the Set-Cookie jwt carries the new user's id, not marta's
|
||||
|
||||
Scenario: A failure after the user is created leaves the invite pending and no user behind
|
||||
Given a pending invite and the invite repository set to fail marking it accepted
|
||||
Scenario: A failure while accepting rolls back and leaves the invite pending and no user behind
|
||||
Given a pending invite and the accept operation of the invite repository set to fail
|
||||
When the client sends POST /v1/auth/invite/accept with username "lea" and password "limewash2026"
|
||||
Then the response status is 500
|
||||
And the user insert and the invite update are rolled back together
|
||||
And no user "lea" exists, no jwt cookie is set and the invite is still pending
|
||||
|
||||
Scenario: The accept endpoints are rate-limited
|
||||
|
||||
Reference in new issue
Block a user