Skip to content

Build your personal knowledge base with Trilium Notes

1.9 KB
Raw Blame
import { cpSync } from "fs";
import { join } from "path";

import { createBaseConfig } from "../../packages/trilium-e2e/src/base-config";

const port = process.env["TRILIUM_PORT"] ?? "8082";
const baseURL = process.env["BASE_URL"] || `http://127.0.0.1:${port}`;

// Copy the test fixture database into the spec/db data directory so the
// server finds it as a regular file-backed database. In CI the workflow
// handles this, but for local runs we do it here.
if (!process.env.TRILIUM_DOCKER) {
    try {
        cpSync(
            join(__dirname, "../../packages/trilium-core/src/test/fixtures/document.db"),
            join(__dirname, "spec/db/document.db")
        );
    } catch (e) {
        // The config is re-evaluated in every worker process; by then the webServer already
        // holds the database open, which makes the (redundant) copy fail on Windows.
        console.warn("Skipping test database copy:", (e as Error).message);
    }
}

export default createBaseConfig({
    appDir: __dirname,
    localTestDir: "e2e",
    projectName: "server",
    // All workers share a single server instance and user account, and some state is
    // global to the account — e.g. the openNoteContexts option holding the open tabs.
    // With parallel workers, every test that opens a note overwrites that state for the
    // others, which chronically flaked "Tabs are restored in right order". Same setting
    // as the standalone app, which runs the identical shared suite without flaking.
    workers: 1,
    webServer: !process.env.TRILIUM_DOCKER ? {
        command: "pnpm start-prod-no-dir",
        url: baseURL,
        reuseExistingServer: !process.env.CI,
        cwd: __dirname,
        env: {
            TRILIUM_DATA_DIR: "spec/db",
            TRILIUM_PORT: port,
            TRILIUM_INTEGRATION_TEST: "memory",
        },
        timeout: 5 * 60 * 1000
    } : undefined,
});