Skip to content

Splitting sdk-test out of Test Suite - #5854

Open
JasonAtClockwork wants to merge 11 commits into
masterfrom
jlarabie/shard-test-suite
Open

Splitting sdk-test out of Test Suite#5854
JasonAtClockwork wants to merge 11 commits into
masterfrom
jlarabie/shard-test-suite

Conversation

@JasonAtClockwork

@JasonAtClockwork JasonAtClockwork commented Sep 1, 2026

Copy link
Copy Markdown
Contributor

Description of Changes

First step to #5839 splitting out the SDK tests and partition:

  • Added cargo ci sdk-tests command for local SDK test execution
  • Split Rust SDK tests out of the main Test Suite job
  • Added a build job that precompiles SDK modules and prepares reusable client artifacts
  • Created separate native and browser nextest archives and client artifacts
  • Sharded native and browser SDK tests into two partitions each

API and ABI breaking changes

No breaking changes - only tests

Rollback safety impact

n/a

Expected complexity level and risk

2 - Splitting up requires CI work and mucking with test setup for preparing clients

Testing

  • Manual test of each partition
  • Full local run of sdk-test to confirm no major issues
  • Utilizing CI to fully test

Comment thread .github/workflows/ci.yml Outdated

sdk_test_build:
needs: [upload-build-artifacts-linux]
name: Build SDK tests

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This job currently takes 13m in the latest CI run. I believe that's probably because of the current spacetimedb-testing dependency which compiles most of standalone.

Ideally we'd like to be able to just download and use the CLI and standalone binaries that are produced by the "Upload build artifacts" job.

I haven't looked into which parts of spacetimedb-testing the sdk test suite is using and how hard it would be to remove this dependency, but that's probably worth looking into. Alternatively we could wait for CI runner image cache which should reduce this build time significantly.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants