Skip to content

🔧 restore HTTP-level e2e for the org membership lifecycle (addMember→accept→promote→leave) #3835

@PierreBrisorgueil

Description

@PierreBrisorgueil

Cross-PR review 2026-06-11: P4 deleted the invite-lifecycle e2e (the only HTTP coverage for promote/leave); P5a replaced it with mocked unit + model-integration tests. NOTHING exercises POST /members, GET /members/search (its before-:memberId route-ordering claim), PUT /membership-requests/:id/accept (auth-only-no-CASL wiring), promote, or leave through real routes/passport/CASL/param middleware. Write organizations.memberAdd.e2e.tests.js: signup A (owner) + B → A searches B by email → addMember → B accepts → A promotes B → B leaves. (The invitations module's own e2e is the model to follow.)
Refs: #3812, #3813, epic #3808.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions