E2E tests: marketplace invest, verify, and settle (mocked externals)

[Jayrodri088]

Context

Regressions in invoice → marketplace → invest → verify → settle are expensive. An automated E2E API test (Supertest) with mocked Stellar, IPFS, and email proves the core product path stays intact as features land.

Complexity & points

High — 200 points

Prerequisites (must be merged or satisfied first)

• Bootstrap Express API: response envelope, errors, health, /api/v1 #5 — Running app factory for tests.
• Stellar wallet challenge-verify auth and JWT sessions #2 — Auth flow testable (challenge/verify mocked or shortened test helper).
• Invoice CRUD, seller authz, and publish lifecycle #3 — Invoice CRUD + publish.
• Marketplace listing API (published invoices, filters, pagination) #4 — Marketplace listing.
• Investment commitments: fractional funding and DB concurrency safety #6 — Create investment.
• Stellar Horizon payment verification and idempotent DB reconciliation #7 — Confirm investment via tx verification (mock Horizon).
• Settlement flow: funded to settled, pro-rata investor returns #9 — Settlement transitions and pro-rata math.

Unblocks (downstream)

• Safe refactors across invoice, marketplace, Stellar, and settlement code with CI signal.

Goals

• One (or a small suite of) E2E test file(s) under tests/e2e/ that:
  • Bootstraps the app with test DB or sqlite if project standard allows—prefer PostgreSQL test container or documented local test DB consistent with TypeORM.
  • Mocks external IO: Stellar Horizon, Pinata/IPFS.
  • Flow: register/auth user(s) → seller creates + publishes invoice → investor lists marketplace → invests → verification marks confirmed → settlement completes.
• CI: npm test runs E2E in CI or a documented npm run test:e2e gated by env (README update).

Out of scope

• Browser/UI tests.
• Mainnet transactions.

Contributor workflow

• Apply on Drips before opening a PR: Claim this issue through the Drips platform before you open a pull request. Unsolicited PRs from unassigned contributors may be closed without review.
• ETA required: Your application must include an ETA for when you will open the first draft PR.
• Draft PR within 24 hours: If a draft PR is not linked on this issue within 24 hours of assignment, maintainers may unassign you so someone else can take the issue.

Acceptance criteria

• E2E passes locally with documented one-time setup.
• No real secrets required for CI mocks.
• Failure messages point to which step of the flow broke.

PR submission requirements

• CI: All GitHub Actions workflow runs for this PR must pass (green) before merge; failing checks block merge.
• PR description must include: Closes #18 (adjust if needed).
• If prerequisites are not all on main, state base branch and merge plan.

[Sammyowase]

@Sammyowase has applied to work on this issue as part of the Stellar Wave Program's 3rd wave.

I've gone through your requirement thoroughly, I will fix this issues and implement a clean pull request to match your acceptance criteria.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Sammyowase to this issue.

[aadviksinghdebug]

@aadviksinghdebug has applied to work on this issue as part of the Stellar Wave Program's 3rd wave.

Hi, I’d like to take this issue .
I’ve worked on similar projects before and have relevant experience, so I should be able to handle this efficiently

ℹ️ Repo Maintainers: To accept this application, review their application or assign @aadviksinghdebug to this issue.