XChain Platform E2E Test Suite

What is xchain-e2e-test

xchain-e2e-test is the end-to-end Mocha test suite for the XChain Platform. It exercises the full platform stack — encoder, decoder, indexer, explorer, hub, UTXO tracker, and regtest miner — against a live regtest deployment. Tests are not mocked; they broadcast real transactions to a regtest coin node and verify that the platform processes them correctly end to end.

The suite also serves as its own quality gate: a comprehensive set of unit, integration, boundary, fuzz, chaos, regression, mutation, and performance tests validate the test framework’s internal infrastructure — connectors, wallet management, transaction helpers, database polling, and bootstrap orchestration — ensuring that the E2E suite itself is reliable before trusting its results for platform validation.

How It Works

Each action test follows the same lifecycle:

1. Create wallets — BIP39 mnemonics and BIP32 derivation paths generate deterministic test wallets programmatically via cryptoHelper.js
2. Fund addresses — the regtest miner’s send_funds JSON-RPC method sends coins to the test wallet addresses
3. Construct and broadcast — the encoder builds a PSBT for the desired XChain action; the test signs the PSBT locally with bitcoinjs-lib and broadcasts it via the coin node
4. Mine — the regtest miner detects the mempool transaction and mines a block (with a configurable delay to batch related transactions like P2SH fund + spend pairs)
5. Poll and verify — the test polls the indexer MariaDB via waitFor* methods until the ACTION record appears, then asserts the expected token state, balances, or transaction status

Features

• 27 ACTION test suites — ISSUE (V0–V5), SEND (V0–V3), MINT, DESTROY, ORDER, DISPENSER, SWAP, DIVIDEND, AIRDROP, FILE, MESSAGE, BROADCAST, ADDRESS, LINK, LIST, CALLBACK, BATCH, SWEEP, SLEEP, COINPAY, STAKE, DEPLOY, EXECUTE, DEPOSIT, WITHDRAW
• 7 service connectors — BlockchainConnector (cross-fetch, Basic Auth), XChainUtxoTrackerConnector, XChainEncoderConnector, XChainIndexerConnector, XChainHubConnector (multi-endpoint failover), RegtestMinerConnector, and Database (MariaDB connection pool)
• Hub auto-discovery — falls back to xchain-hub for service endpoint resolution when direct environment variables are not set
• Multi-chain support — Bitcoin, Litecoin, and Dogecoin on regtest (network configs via CryptoNetworks.js)
• P2SH two-step encoding — transactionHelper.js detects when the encoder returns encoding: "P2SH" and automatically handles the two-transaction flow (fund + spend)
• UTXO verification cache — tracks confirmed UTXOs between sequential transactions for the same address to avoid stale mempool entries
• 30+ database polling methods — waitForIssue, waitForSend, waitForCredit, waitForDebit, waitForMint, waitForDispenser, waitForOrder, etc., each with configurable timeout and performance tracking
• Wallet memory cleanup — seed and private key buffers are zeroed during afterAll teardown
• Performance instrumentation — nanosecond-precision bootstrap phase timing, per-poll metrics, custom Mocha reporter writing JSON to perf-results/
• Mutation testing — Stryker Mutator with two-phase configuration (Phase 1: unit tests, Phase 2: unit + integration)
• 953+ tests across 11 testing disciplines

Architecture

Service Connector Layer

The test suite communicates with 7 platform services through dedicated connector classes:

┌─────────────────────────────────────────────────────────────────┐
│  xchain-e2e-test                                                │
│                                                                  │
│  ┌──────────────┐  ┌──────────────┐  ┌──────────────────────┐  │
│  │ cryptoHelper  │  │ transaction  │  │ action helpers       │  │
│  │ BIP39/BIP32   │  │ Helper       │  │ (27 modules)         │  │
│  │ wallet mgmt   │  │ PSBT/P2SH    │  │ message construction │  │
│  └──────┬───────┘  └──────┬───────┘  └──────────┬───────────┘  │
│         │                 │                      │               │
│  ┌──────▼─────────────────▼──────────────────────▼───────────┐  │
│  │              Service Connectors (src/)                     │  │
│  │  BlockchainConnector     XChainEncoderConnector            │  │
│  │  XChainUtxoTrackerConn   XChainIndexerConnector            │  │
│  │  XChainHubConnector      RegtestMinerConnector             │  │
│  │  Database (MariaDB)                                        │  │
│  └──────────────────────────┬────────────────────────────────┘  │
│                             │                                    │
└─────────────────────────────┼────────────────────────────────────┘
                              │  HTTP / JSON-RPC / MariaDB
┌─────────────────────────────▼────────────────────────────────────┐
│  LIVE REGTEST SERVICES                                            │
│  • bitcoind/litecoind/dogecoind    • xchain-decoder               │
│  • xchain-utxo-tracker            • xchain-indexer + MariaDB      │
│  • xchain-encoder                 • xchain-hub                    │
│  • xchain-regtest-miner                                           │
└───────────────────────────────────────────────────────────────────┘

Bootstrap Sequence

The initialCheck.test.js Mocha root hook runs four phases before any test:

Polling Pattern

All waitFor* methods in db.js follow the same pattern:

1. Record start time and poll count
2. Loop while Date.now() < endTime (default 30 seconds)
3. Call the corresponding check* method (parameterized SQL query)
4. If a row is found, record performance metrics and return the row
5. If not found, sleep 1 second and retry
6. On timeout, record metrics and return null

Teardown

The afterAll hook restores default mining timing, zeroes wallet seed and private key buffers, and closes the MariaDB connection pool.

Test Structure

Action Tests (Live)

Tests are ordered and stateful. Later tests depend on wallets, tokens, and actions created by earlier tests. The suite is designed to run as a single sequential pass from start to finish.

Action test files are organized by type in test/actions/:

• Token lifecycle: ISSUE, MINT, SEND, DESTROY
• DEX: ORDER, DISPENSER, SWAP, COINPAY
• Distribution: DIVIDEND, AIRDROP
• Data: FILE, MESSAGE, BROADCAST
• Configuration: ADDRESS, LINK, LIST, CALLBACK
• Multi-action: BATCH
• Control: SWEEP, SLEEP
• Smart contracts: DEPLOY, EXECUTE, DEPOSIT, WITHDRAW
• Staking: STAKE, UNSTAKE, DELEGATE, COLLECT

Infrastructure Tests (No Live Services Required)

The test framework’s own infrastructure is validated by tests that run without Docker or live services:

Live Infrastructure Tests

Configuration

The test suite resolves configuration in priority order:

1. Direct environment variables (17 variables for all service endpoints)
2. Hub discovery — if direct env vars are missing, queries HUB_URL/HUB_PORT for service config
3. Docker defaults — database host defaults to "mariadb" (Docker Compose convention)

See Configuration for the full environment variable reference.

Running the Tests

The full regtest stack must be running for action tests, E2E tests, and smoke tests. Unit, integration, boundary, fuzz, chaos, and regression tests run without any external services.

# Full action test suite (requires live stack)
npm test

# Infrastructure tests (no services required)
npm run test:unit
npm run test:integration
npm run test:regression:p0    # Critical-path gate, < 500ms

# All infrastructure tests
npm run test:regression       # Full regression (114 tests)
npm run test:boundary
npm run test:fuzz
npm run test:chaos

Documentation

Related

• Regtest Development Guide — setting up a local regtest environment
• Regtest Miner — the auto-mining service the E2E suite depends on
• Encoder — constructs XChain transactions tested by this suite
• Indexer — processes transactions and maintains token state verified by this suite
• Testing Guide — platform-wide testing philosophy and coverage

Copyright © 2025–2026 Dankest, LLC

Based on XChain Platform by Dankest, LLC – https://dankest.llc

Licensed under the GNU Affero General Public License v3.0 (AGPL-3.0-or-later) with a commercial license available for proprietary use.

You may use, modify, and distribute this material under the terms of the License. See LICENSE and NOTICE for full terms. See the licensing overview.