Skip to content

Add mocked post-deployment smoke test flow #399

Description

@El-swaggerito

Description

Difficulty: Expert

Type: Testing

Summary

Add a mocked smoke test flow for the deployed vault lifecycle.

Current Behaviour

The real smoke test will be run by the maintainer after testnet deployment, but the repo needs a safe mocked flow first.

Expected Behaviour

The mocked flow should cover deployed contract ID loading, initialization input loading, read verification, and lifecycle expectation checks.

Suggested Implementation

Create mocked fixtures, tests, docs, examples, and script output for the post-deployment smoke test flow.

Files or Areas Likely Affected

  • scripts
  • examples
  • docs
  • schemas
  • contracts/vault-contract/tests

Acceptance Criteria

  • Mocked post-deployment smoke flow is added.
  • Mocked contract ID loading is included.
  • Mocked initialization input loading is included.
  • Expected lifecycle checks are documented.
  • Tests validate the mocked smoke flow or fixtures.
  • Example output is included.
  • No live RPC calls or secrets are used.
  • cargo fmt, cargo check, cargo test, and cargo clippy pass.

Additional Notes

Do not call Stellar testnet in this issue.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Third CampaignThird Campaign issuecontractsSoroban contract workcontributor-safeCan be completed without secrets or privileged accessdeploymentDeployment readiness and release preparationdocsDocumentation workexamplesExample files and usage referencesexpertExpert difficultymaybe-rewardedMay be eligible for contributor rewards after maintainer reviewmocked-flowMocked flow or dry-run implementationnetworkNetwork and protocol layer worksmoke-testSmoke test scripts and validation flowstestnet-readyPreparation for future testnet usagetestsTesting coverage

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions