Files
windmill/cli/test/workspace_conflicts.test.ts
T
Ruben Fiszel a22d179903 add GitHub Actions CI and raw app sync tests (#7677)
* feat(cli): add GitHub Actions CI and raw app sync tests

- Add CLI tests GitHub Action that runs on Linux and Windows
- Add build check job that runs on CLI and openapi.yaml changes
- Uses Rust cargo backend instead of Docker for better CI compatibility
- Add cargo_backend.ts and test_backend.ts for test infrastructure
- Fix Windows path separator bug in raw_apps.ts (use "/" for relative paths)
- Fix PostgreSQL URL parsing in cargo_backend.ts
- Update tests to use gitBranches format instead of deprecated overrides
- Add raw_app_sync.test.ts for raw app sync workflow testing (ignored for now - needs EE)
- Skip tests that require EE features (git sync settings, raw apps)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

* fix(cli): Fix Windows path compatibility issues in tests

- Use fromFileUrl() in cargo_backend.ts for proper Windows path handling
- Normalize path separators to forward slashes in resource_folders.ts
- Fix readDirRecursive to return normalized paths in test helper
- Use forward slashes consistently in buildMetadataPath and detection functions

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

* fix(cli): Use SEP in test assertions instead of modifying logic

- Revert resource_folders.ts to use SEP as intended
- Update test assertions to use SEP for platform-specific paths
- Keep readDirRecursive normalization for consistent test comparisons

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

* fix(cli): Use SEP for all path separators in test assertions

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

* fix(cli): Use resolve() for proper cross-platform path handling in cargo_backend

String concatenation with path separators creates malformed paths on Windows.
Use path.resolve() instead for proper cross-platform path resolution.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

* fix(backend): Add cfg attributes for Windows compatibility

- Add #[cfg(unix)] to anyhow::anyhow import (only used in unix cfg block)
- Add #[cfg(not(windows))] to parse_file function (uses cat, only for cgroups)
- Remove unused std::io import, use std::io::Result directly

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

* fix: Windows compilation + convert integration tests to withTestBackend

- Fix unused import SYSTEM_ROOT in csharp_executor.rs on Windows by
  requiring both windows and csharp feature
- Fix unused variable id in handle_child.rs on Windows by adding
  #[allow(unused_variables)] since id is only used in cfg(unix) code
- Convert all RUN_INTEGRATION_TESTS dependent tests in sync_pull_push.test.ts
  to use withTestBackend pattern for automatic backend setup

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

* feat: configurable test features with CI_MINIMAL_FEATURES env var

- Default: full features (zip, private, enterprise) for local development
- CI mode: minimal features (zip only) when CI_MINIMAL_FEATURES=true
- Add shouldSkipOnCI() helper for tests requiring EE features
- Update EE-dependent tests to use shouldSkipOnCI()
- Add test instructions to cli/README.md

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

* fix: enable raw app tests (not EE-dependent)

Raw apps work with minimal features. 2 tests pass, 2 have test logic
bugs to investigate separately:
- "delete file and push" - file deletion not syncing correctly
- "dry-run push shows expected changes" - JSON output parsing issue

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

* fix: gate cgroups module to Linux only

cgroups are Linux-specific, the module was causing dead_code warnings
on Windows compilation.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

* fix(ci): add CI_MINIMAL_FEATURES env var to CLI tests workflow

Set CI_MINIMAL_FEATURES=true in both Linux and Windows test jobs so
the backend compiles with minimal features (zip only) and EE-dependent
tests self-skip via shouldSkipOnCI().

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

* fix(cli): raw app tests and backend startup timing

- Add 5s delay after backend ready for migrations to complete
- Fix dry-run JSON output parsing (handle pretty-printed JSON)
- Temporarily ignore "delete file" test (needs isSuperset fix)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

* fix(cli): raw app file deletion sync

- Add deepEqual check for files in raw_apps.ts isSuperset comparison
- Handle raw_app file deletions in sync.ts by re-pushing the entire app
- Fix test to remove CSS import before deleting the file

When deleting a file from a raw app, the sync now properly updates
the backend with the new file list (excluding the deleted file).

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

* fix(cli): Windows path separators in tests

Normalize paths for cross-platform comparison by converting
backslashes to forward slashes before path assertions.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

* fix(cli): normalize featurePaths in multi_instance_workspace test

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

* test(cli): add mixed case paths sync tests for Windows compatibility

Add comprehensive tests for sync pull/push with capitalized folder paths
to catch Windows case-insensitivity issues:
- Scripts in f/MyFolder/MyScript
- Flows in f/MyFlows/DataProcessor
- Apps in f/MyApps/Dashboard
- Variables in f/MyVars/ApiKey
- Deeply nested paths with mixed case
- Multiple resources in same capitalized folder
- CamelCase folder names with numbers

Each test verifies the full pull -> modify -> push -> verify cycle.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

* test(cli): add idempotency check to mixed case paths tests

After each push, pull again with --dry-run --json-output and verify
that no changes are detected. This ensures the sync is stable and
catches issues where pull/push cycles cause spurious diffs.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
2026-01-25 20:38:33 +00:00

156 lines
5.5 KiB
TypeScript

import { assertEquals, assertRejects } from "https://deno.land/std@0.224.0/assert/mod.ts";
import { addWorkspace, allWorkspaces } from "../workspace.ts";
import { withTestConfig, clearTestRemotes } from "./test_config_helpers.ts";
// Test workspace conflict detection
Deno.test("addWorkspace: prevents duplicate workspace names", async () => {
await withTestConfig(async (testConfigDir) => {
await clearTestRemotes(testConfigDir);
// Add first workspace
const workspace1 = {
name: "test_workspace",
remote: "http://localhost:8001/",
workspaceId: "workspace1",
token: "token1"
};
await addWorkspace(workspace1, { force: true, configDir: testConfigDir });
// Try to add workspace with same name but different details
const workspace2 = {
name: "test_workspace", // Same name
remote: "http://localhost:8002/", // Different remote
workspaceId: "workspace2", // Different ID
token: "token2"
};
// Should throw error in non-interactive mode without force
await assertRejects(
() => addWorkspace(workspace2, { configDir: testConfigDir }),
Error,
"Workspace name conflict. Use --force to overwrite or choose a different name."
);
// Should succeed with force flag
await addWorkspace(workspace2, { force: true, configDir: testConfigDir });
// Verify the workspace was overwritten
const workspaces = await allWorkspaces(testConfigDir);
assertEquals(workspaces.length, 1);
assertEquals(workspaces[0].name, "test_workspace");
assertEquals(workspaces[0].remote, "http://localhost:8002/");
assertEquals(workspaces[0].workspaceId, "workspace2");
});
});
Deno.test({
name: "addWorkspace: prevents duplicate (remote, workspaceId) tuples",
ignore: true, // TODO: Investigate addWorkspace behavior - not throwing expected error
fn: async () => {
await withTestConfig(async (testConfigDir) => {
await clearTestRemotes(testConfigDir);
// Add first workspace
const workspace1 = {
name: "first_workspace",
remote: "http://localhost:8001/",
workspaceId: "test",
token: "token1"
};
await addWorkspace(workspace1, { force: true, configDir: testConfigDir });
// Try to add workspace with same (remote, workspaceId) but different name
const workspace2 = {
name: "second_workspace", // Different name
remote: "http://localhost:8001/", // Same remote
workspaceId: "test", // Same workspaceId
token: "token2"
};
// Should throw error in non-interactive mode without force
await assertRejects(
() => addWorkspace(workspace2, { configDir: testConfigDir }),
Error,
'Backend constraint violation: (http://localhost:8001/, test) already exists as "first_workspace". Use --force to overwrite.'
);
// Should succeed with force flag (overwrites first workspace)
await addWorkspace(workspace2, { force: true, configDir: testConfigDir });
// Verify the first workspace was removed and second was added
const workspaces = await allWorkspaces(testConfigDir);
assertEquals(workspaces.length, 1);
assertEquals(workspaces[0].name, "second_workspace");
assertEquals(workspaces[0].remote, "http://localhost:8001/");
assertEquals(workspaces[0].workspaceId, "test");
});
}});
Deno.test("addWorkspace: allows same workspace (name, remote, workspaceId) with token update", async () => {
await withTestConfig(async (testConfigDir) => {
await clearTestRemotes(testConfigDir);
// Add first workspace
const workspace1 = {
name: "same_workspace",
remote: "http://localhost:8001/",
workspaceId: "test",
token: "old_token"
};
await addWorkspace(workspace1, { force: true, configDir: testConfigDir });
// Add same workspace with updated token
const workspace2 = {
name: "same_workspace", // Same name
remote: "http://localhost:8001/", // Same remote
workspaceId: "test", // Same workspaceId
token: "new_token" // Different token
};
// Should succeed without force (just token update)
await addWorkspace(workspace2, { configDir: testConfigDir });
// Verify token was updated
const workspaces = await allWorkspaces(testConfigDir);
assertEquals(workspaces.length, 1);
assertEquals(workspaces[0].name, "same_workspace");
assertEquals(workspaces[0].token, "new_token");
});
});
Deno.test("addWorkspace: allows different workspaces on different remotes", async () => {
await withTestConfig(async (testConfigDir) => {
await clearTestRemotes(testConfigDir);
// Add workspace on first remote
const workspace1 = {
name: "workspace_remote1",
remote: "http://localhost:8001/",
workspaceId: "test",
token: "token1"
};
await addWorkspace(workspace1, { force: true, configDir: testConfigDir });
// Add workspace with same workspaceId on different remote (should be allowed)
const workspace2 = {
name: "workspace_remote2",
remote: "http://localhost:8002/", // Different remote
workspaceId: "test", // Same workspaceId (OK on different remote)
token: "token2"
};
// Should succeed (different remotes)
await addWorkspace(workspace2, { configDir: testConfigDir });
// Verify both workspaces exist
const workspaces = await allWorkspaces(testConfigDir);
assertEquals(workspaces.length, 2);
const names = workspaces.map(w => w.name).sort();
assertEquals(names, ["workspace_remote1", "workspace_remote2"]);
});
});