Testing & Fixtures

The repo ships batteries-included testing utilities so SDKs or downstream libraries can verify behavior without hitting the live network.

Mock live service

import { MockLiveServiceClient } from "@qubiq/core/testing";

const mock = new MockLiveServiceClient();
mock.enqueueBalance("SUZ...", { balance: "1000" });
expect((await mock.getBalance("SUZ...")).balance.balance).toBe("1000");

Swap the mock into your unit tests to avoid network calls.

Snapshot fixtures

import { HistoricalTickSnapshots, replayTickSnapshots } from "@qubiq/core/testing";

await replayTickSnapshots(HistoricalTickSnapshots, async (sample) => {
  console.log(sample.tick);
}, { delayMs: 10 });

Fixtures cover both tick metadata and transaction histories (HistoricalTransactionSnapshots). Use them to stress pipelines or serialization logic deterministically.

Replay helpers

import { replayTransactionSnapshots } from "@qubiq/core/testing";

await replayTransactionSnapshots(HistoricalTransactionSnapshots, async (tx) => {
  queue.enqueue({ destinationPublicKey: tx.destination, amount: BigInt(tx.amount) });
}, { loop: true, delayMs: 5 });

Replays respect abort signals and loop options so you can simulate busy periods.

Smoke tests

Two opt-in tests hit public endpoints to ensure connectivity:

QUBIC_SMOKE_TESTS=true bun test tests/smoke/live-service-smoke.test.ts

They fetch /v1/tick-info and /v1/balances/{id} using the production API. Keep them off in CI unless you explicitly need to validate environments.

Helpful commands

Check tests/automation, tests/wallet, tests/proposals, and tests/serialization for real examples of mocking + replay patterns.