Stone.js API
    Preparing search index...

    Interface TestConfig

    Configuration for the test run, under stone.builder.test.

    Tests are a context like any other, so they are configured in the same file as the build: a project needs no second config file to keep in sync with the first.

    interface TestConfig {
        envFile?: string;
        include?: string[];
        pattern?: string;
        vitest?: Record<string, unknown>;
    }
    Index
    envFile? include? pattern? vitest?
    envFile?: string

    The env file to load before the runner starts, so a value read at module load sees it. Defaults to .env.test. It takes precedence over .env, which is already loaded by then.

    include?: string[]

    The files to treat as test suites. Defaults to ./tests/** matching .test. / .spec. in js/ts, with or without JSX.

    pattern?: string

    The files createTestApp() discovers the application from. Defaults to whatever the build scans, which is the point: the suite boots what ships.

    vitest?: Record<string, unknown>

    Escape hatch: raw Vitest config, merged over the defaults, exactly as vite and rollup are. This is where a frontend project switches environment to happy-dom for component tests.

    Settings
    Member Visibility

    On This Page
    Properties