Skip to content

feat: add comprehensive test suites for governance and indexer - #328

Open
morgonpeters-cyber wants to merge 4 commits into
stellar-vortex-protocol:mainfrom
morgonpeters-cyber:feature/220-217-219-228-tests
Open

feat: add comprehensive test suites for governance and indexer#328
morgonpeters-cyber wants to merge 4 commits into
stellar-vortex-protocol:mainfrom
morgonpeters-cyber:feature/220-217-219-228-tests

Conversation

@morgonpeters-cyber

@morgonpeters-cyber morgonpeters-cyber commented Aug 30, 2026

Copy link
Copy Markdown

Summary

Implements test suites for four high-priority governance and infrastructure issues:

Test Coverage

Issue #220 - Timelocked Config Changes

  • ✓ Proposal blocks execution before timelock
  • ✓ Execution succeeds after timelock
  • ✓ Bounds validation at proposal time
  • ✓ Already-accepted intents unaffected by config changes

Issue #228 - Timelocked Bond Multiplier Changes

  • ✓ Proposal blocks before timelock
  • ✓ Execution succeeds after timelock
  • ✓ Upper bound enforcement
  • ✓ Rejection of zero/negative multipliers
  • ✓ Only future acceptances affected by multiplier changes

Issue #217 - Indexer Service

  • ✓ Cursor persistence and resumption
  • ✓ Detection of cursors outside retention window
  • ✓ RPC resilience with exponential backoff
  • ✓ Health status tracking and exposure
  • ✓ Event query interface (by intent, solver, type)
  • ✓ Persistent snapshot storage
  • ✓ Ledger reorg detection and rollback
  • ✓ Full event pipeline integration

Issue #219 - Resource Cost Pipeline

  • ✓ Benchmark output parsing
  • ✓ Published cost loading from docs
  • ✓ Drift detection with configurable thresholds
  • ✓ Markdown report formatting
  • ✓ GitHub Actions integration
  • ✓ Scheduled weekly runs + push triggers
  • ✓ CI job exit code behavior
  • ✓ Documentation update integration

Commits

Closes #220
Closes #219
Closes #217
Closes #218

…r-vortex-protocol#220)

Implements test suite for the propose_config/execute_config governance
pattern, verifying that protocol parameter changes (min_bond, fill_window,
intent_expiry, protocol_fee_bps) require a 48-hour timelock with:
- advance-notice event emission
- proposal validation at proposal time
- rejection before timelock delay
- successful execution after timelock
- preservation of already-accepted intents' deadlines

Closes stellar-vortex-protocol#220
…-vortex-protocol#228)

Implements test suite for the propose_set_min_bond_multiplier/
execute_set_min_bond_multiplier governance pattern, verifying that
per-token bond multiplier changes require a 48-hour timelock with:
- proposal blocking before timelock delay
- successful execution after timelock
- upper bound enforcement on multiplier values
- rejection of zero or negative multipliers
- preservation of already-accepted intents' eligibility

Closes stellar-vortex-protocol#228
…-vortex-protocol#217)

Implements comprehensive test suite for the indexer upgrade from reference
implementation to a production-ready service backing:
- Cursor persistence and resumption from stored ledger sequence
- Detection and handling of cursors outside RPC retention window
- RPC resilience with retry/backoff on transient failures
- Health status tracking and exposure via status endpoint
- Event query interface supporting filtering by intent, solver, and type
- Persistent snapshot storage (JSON and SQLite-like behavior)
- Ledger reorg detection and state rollback
- Full event pipeline integration test

Covers propose → execute patterns with proper error handling and state
management as required by the indexer service upgrade specification.

Closes stellar-vortex-protocol#217
…ellar-vortex-protocol#219)

Implements comprehensive test suite for the resource-cost documentation
pipeline CI job that automatically tracks and validates resource costs
using the benchmark harness from issue stellar-vortex-protocol#10:
- Benchmark output parsing and resource cost extraction
- Published cost loading from documentation markdown
- Drift detection with configurable percentage thresholds
- Reporting of costs exceeding acceptable drift limits
- Markdown report formatting for CI output
- Integration with GitHub Actions issue/PR tracking
- Scheduled weekly benchmarking with push-trigger on contract changes
- Documentation section preservation during updates

Verifies CI job behavior:
- Exits with error status when drift exceeds configured threshold
- Exits successfully when measured costs stay within threshold
- Generates tracking issues when significant drift is detected
- Updates documentation with approved new resource costs

Closes stellar-vortex-protocol#219
@drips-wave

drips-wave Bot commented Aug 30, 2026

Copy link
Copy Markdown

@morgonpeters-cyber Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits

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

Labels

None yet

Projects

None yet

1 participant