Acceptance Test Suite is missing

[DeepDiver1975]

We need to ensure that all functions of the mcp server are properly behaving - including exceptional scenarios.

The acceptance test suite shall start an ocis server via docker. Based on acceptance test suite in owncloud/ocis tools exist to setup the server environment (users, files, folders, shares etc).

Each mcp_server function mus have it's own test suite

[dj4oC]

Thanks for filing this, @DeepDiver1975.

Area affected: testing/CI infrastructure, cross-cutting across all of internal/tools/*.go (~50 tools: shares, spaces, files, groups, users, workflows, settings, etc.).

Current state: the repo has unit tests per tool file (e.g. internal/tools/shares_test.go, spaces_test.go, files_test.go, ...), but these all mock the oCIS Graph API with httptest.Server and assert request/response shapes in isolation. There is no suite that exercises the MCP server end-to-end against a real, running oCIS instance — so nothing today catches integration-level regressions (auth flows, real Graph API response drift, WebDAV behavior, multi-step workflows spanning several tools).

Severity: missing feature / test-infrastructure gap — not a bug in a specific tool, but a real coverage risk. Several past bugs (e.g. #11's wrong API version prefix, the share-invite {"value":[...]} vs {"permissions":[...]} envelope mismatch fixed in #24) were only caught by manual verification against a live oCIS instance, which is exactly what an automated acceptance suite would have caught pre-merge.

To move this forward, it would help to know:

• Should this reuse tooling/patterns from owncloud/ocis's existing acceptance test suite (e.g. its Behat-based setup or the environment bootstrap scripts for users/files/shares), or would a Go-native approach (e.g. testcontainers-go spinning up the oCIS docker image) be preferred?
• Is the intent one acceptance test per MCP tool (~50 suites), or grouped by domain matching the existing internal/tools/*.go files?
• Any target oCIS version to pin the docker image to for CI reproducibility?

Related: #13 (Graph SDK migration, partially addressed in #24) surfaced several of the bug classes this suite should guard against going forward.

🤖 Automated triage by Claude Code

---

Generated by Claude Code