Skip to content

test: Write E2E test for full contributor lifecycle: apply, get assigned, complete #662

Description

@FaveTeamz

Summary

There is no end-to-end test that covers the complete happy path of a contributor lifecycle: applying for an issue, being assigned by a maintainer, and having the assignment marked complete. Each step is tested in isolation but not as a continuous flow.

Problem

Integration points between steps (counter consistency, state transitions) can have bugs that only appear when the full flow runs sequentially. Unit tests with mocked state cannot catch these cross-step bugs.

Acceptance Criteria

  • Write an E2E test against a local Stellar Quickstart node (or testnet)
  • Flow: setup (register org, register maintainer) → contributor applies → maintainer assigns → maintainer completes → verify contributor org assignment count = 0, global app count = 0
  • Assert all intermediate states: after apply (app count = 1), after assign (org assign count = 1), after complete (both counters = 0)
  • Test must run in CI using the contract-e2e GitHub Actions workflow
  • Include teardown to restore contract to clean state for subsequent test runs
  • Document the test in docs/testing.md under the E2E section

Metadata

Metadata

Labels

Stellar WaveIssues in the Stellar wave programtestingTests

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions