Testing

Run Clarity contract tests and frontend Vitest suites with stacksdapp test

stacksdapp test runs contract tests (Clarinet SDK) and frontend tests (Vitest). No Docker or local devnet is required for contract tests.

Contents

• Run all tests
• Contract tests
• ABI caching
• Type-check before testing
• Frontend tests
• Tips

Run all tests

stacksdapp test

This runs:

• Contracts: Vitest + Clarinet SDK (initSimnet()) in contracts/tests/
• Frontend: Vitest in frontend/ (vitest run --passWithNoTests)

Contract tests

Tests live under contracts/tests/.

import { Cl, ClarityType } from "@stacks/transactions";
import { beforeEach, describe, expect, it } from "vitest";
import { initSimnet } from "@stacks/clarinet-sdk";

let simnet: Awaited<ReturnType<typeof initSimnet>>;
let accounts: ReturnType<Awaited<ReturnType<typeof initSimnet>>["getAccounts"]>;
let deployer: string;
let address1: string;

beforeEach(async () => {
  simnet = await initSimnet();
  accounts = simnet.getAccounts();
  deployer = accounts.get("deployer")!;
  address1 = accounts.get("wallet_1")!;
});

describe("counter", () => {
  it("increments", () => {
    const result = simnet.callPublicFn("counter", "increment", [], address1);
    expect(result.result.type).toBe(ClarityType.ResponseOk);
  });
});

Requires Clarinet 3.21+ and matching @stacks/clarinet-sdk in the contracts package.

ABI caching

Contract ABIs are cached under contracts/.cache/. Unchanged sources skip redundant initSimnet runs during generate and test workflows.

Type-check before testing

stacksdapp check

Validates Clarity syntax and types without deployment.

Frontend tests

Frontend Vitest suites live under frontend/. They run as part of stacksdapp test even if you have not written tests yet.

Tips

• Use simnet tests for contract logic
• Use local devnet or testnet for full wallet flows
• After editing contracts, run stacksdapp generate so bindings stay aligned with tests that import generated code