Skip to content

Verification baseline: fixture tests, CI, and operator docs #7

@amichne

Description

@amichne

Summary

Build the verification and release baseline needed to keep semantic and packaging regressions out of the main branch.

Why

Current test coverage is still thin relative to the intended product shape. The visible server tests mostly exercise transport behavior against a fake backend, and the repo does not yet have CI smoke tests for real backend behavior or packaging.

Scope

  • Add fixture-project contract tests shared across fake, IntelliJ, and standalone backends
  • Add standalone bootstrap/compat regression coverage
  • Add rename/reference/diagnostic integration tests on real fixture projects
  • Add Linux and macOS CI smoke tests
  • Add IntelliJ plugin verification and artifact-content checks in CI
  • Add operator guidance for running the standalone backend on real repositories
  • Update docs/remaining-work.md to reflect the current repo state

Done when

  • Real backend behavior is tested against fixture projects
  • CI catches bootstrap, packaging, and compatibility regressions automatically
  • Operator docs exist for real standalone usage
  • docs/remaining-work.md matches the current implementation status

References

  • analysis-server/src/test/kotlin/io/github/amichne/kast/server/AnalysisApplicationTest.kt
  • backend-standalone/src/test/kotlin/io/github/amichne/kast/standalone/StandaloneAnalysisBackendResolveSymbolTest.kt
  • docs/remaining-work.md

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions