import { InlineConfig, VitestEnvironment } from 'vitest/node';
/**
 * A builder for test configurations found in vite's defineConfig test field.
 *
 * @deprecated
 *        Use @zthun/janitor-vite plugins instead.  Those plugins automatically
 *        give test configuration.
 *
 */
export declare class ZViteTestBuilder {
    private test;
    /**
     * Initializes a new instance of this object.
     */
    constructor();
    /**
     * Sets the test environment.
     *
     * @param environment -
     *        The test environment to use.
     *
     * @returns
     *        This object.
     */
    environment(environment: VitestEnvironment): this;
    /**
     * Sets the test environment to "node".
     *
     * @returns
     *        This object.
     */
    node: () => this;
    /**
     * Sets the test environment to "happy-dom".
     *
     * @returns
     *        This object.
     */
    browser: () => this;
    /**
     * Sets the test coverage provider.
     *
     * @param provider -
     *        The test coverage provider to use.
     *
     * @returns
     *        This object.
     */
    coverage(provider: "v8" | "istanbul"): this;
    /**
     * Sets the test coverage provider to "v8".
     *
     * @returns
     *        This object.
     */
    v8: () => this;
    /**
     * Sets the test coverage provider to "istanbul".
     *
     * @returns
     *        This object.
     */
    istanbul: () => this;
    /**
     * Adds to the list of projects.
     *
     * @param project -
     *        The list of projects.
     *
     * @returns
     *        This object.
     */
    project(project?: string | string[]): this;
    /**
     * Adds monorepo support to the test builder.
     *
     * @param packages -
     *        The path to the package directory.
     *
     * @returns
     *        This object.
     */
    monorepo(packages?: string): this;
    /**
     * This sets the max concurrency to one and resets
     * the environment after every test.
     *
     * Use this in the case that you want to have
     * strategic tests that can step over one another. For example,
     * writing to the file system and deleting from the file system
     * can have race conditions.  If your app or library tests heavily
     * depend on those operations, then you should run your tests serially.
     *
     * @returns
     *        This object.
     */
    runSerially(): this;
    /**
     * Returns the built test configuration.
     *
     * @returns
     *        A deep clone of the test configuration.
     */
    build(): InlineConfig;
}