MettaChain/PropChain-contract

Re-enable bridge load tests with deterministic isolation

Closed

#755 opened on Jul 23, 2026

View on GitHubContributor guide
 (4 comments) (0 reactions) (1 assignee)Rust (151 forks)auto 404
High ComplexityRustStellar Wavebughelp wantedperformancetesting

Repository metrics

Stars
 (1 star)
PR merge metrics
 (PR metrics pending)

Description

Problem Statement

tests/bridge_load_tests.rs:226 and tests/integration_bridge_oracle.rs have #[ignore] due to test isolation.

Why it matters

Load tests are the empirical basis for our gas-budget claims; if they're ignored, we have no load signal.

Technical Context

Fix the isolation (#39) then unignore; rewrite load assertions to be deterministic (use Instant::now of mocked env, not wall-clock).

Expected Outcome

Full suite runs in CI; ≥ 10k requests in < 10s documented in result.

Acceptance Criteria

  1. cargo test --release load_test_concurrent_registration_light green.
  2. cargo test --release stress_test_mass_registration green.
  3. Output captured to docs/PERFORMANCE.md.

Implementation Notes

Use per-test Arc<Mutex<…>> harness with set_block_number(0) reset.

Files or modules likely to be affected

tests/bridge_load_tests.rs, tests/integration_bridge_oracle.rs.

Dependencies

#39.

Difficulty level

HARD.

Estimated effort

M (~3 days).

Contributor guide

Research direction
Investigate the isolation failure in tests/bridge load tests.rs and tests/integration bridge oracle.rs, implement deterministic isolation using an Arc<Mutex> harness with set block number(0) reset, rewrite load assertions to use Instant::now from the mocked environment, and then run cargo test release to verify both load test concurrent registration light and stress test mass registration pass.
Tech stack
rust
Domain
backendtesting
Issue type
Test
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
RustCargoTesting
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40