Skip to content

(Epic) Define semantics (and testing strategy) when SDK version is revved #1095

New issue
New issue
Closed
Closed
(Epic) Define semantics (and testing strategy) when SDK version is revved#1095

Description

@MonsieurNicolas

MonsieurNicolas
openedon Aug 3, 2022

This is similar to stellar/rs-soroban-env#310 but scenarios are around SDK changes that are not impacting the core protocol.

Context:

  • contract A and B are compiled with SDK 1.0.0
  • contract A depends on B (ie: A invokes B)

Scenario:

  • A's developer wants to upgrade to SDK 2.0.0 and wants to test what happens when calling B compiled with version 1.0.0
  • B gets recompiled using SDK 2.0.0, A's developer wants to test and understand how A would be impacted.

This is somewhat related to stellar/rs-soroban-env#289

Tasks
Beta Give feedback
  1. Add test utilities that make it easier to test contract consistency over time #1082
    leighmcculloch
  2. Add docs for how to test contract consistency and sdk/env/protocol upgrades stellar-docs#480
    leighmcculloch
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions