clockworklabs / clockworklabs/SpacetimeDB

Test coverage - Backwards-compatibility

Open
#2,387 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Rust
Stars
25.2k
Forks
1.1k
Avg merge
2d 7h
Merged PRs (30d)
46

Description

We should have a CI-run test that adds some data to SpacetimeDB, upgrades to a new version (e.g. current PR), and checks that the upgrade is successful.

Definition of Done

WIP, pls halp

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No file, test, or CI entry point is named. Start by locating the existing CI test setup and any upgrade or compatibility checks, then trace how test data is added to SpacetimeDB and how a new version is selected. Done means a CI-run test verifies that data survives a version upgrade successfully.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
ci-cd, databases, testing
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.