Skip to content

Releases: Karzone/TestAtlas

v0.1.6 — spec-driven authoring tools

Choose a tag to compare

@Karzone Karzone released this 29 Jul 18:52

Adds 6 read-only MCP tools for spec-driven / story→automation authoring — grounding an AI agent in what already exists so it reuses instead of regenerating. MCP server: 5 → 11 tools.

  • resolve_step — resolve a Gherkin phrase to the existing step definition(s) that would bind it (exact/ambiguous/none + shared-term-ranked suggestions).
  • get_scenario / get_step_definition — full detail by name/expression, incl. the scenarios a definition is used by.
  • step_catalog — reusable step vocabulary with extracted placeholders & allowed values.
  • list_tags — tag taxonomy with per-tag scenario counts.
  • project_dependencies — the implied project dependency graph (answers "what depends on ?").

Step-hygiene detection is intentionally left to SpecHygiene; the 5 original tools are unchanged. 247 tests green.

v0.1.5

Choose a tag to compare

@Karzone Karzone released this 29 Jul 15:51

Polishes the README header for the MCP Server Manager / registry display — NuGet version badges, an MCP facts row (transport/auth/hosting), a tools row, and a quick "add to your AI agent" setup block. No CLI or runtime changes.

v0.1.4

Choose a tag to compare

@Karzone Karzone released this 29 Jul 15:33

Lists TestAtlas in the Official MCP Registry, so it appears in Visual Studio's MCP Server Manager (Browse) and other registry-aware MCP clients. Adds the required mcp-name marker to the package README and an automated mcp-publisher step (GitHub OIDC — no secret) to the release workflow. No CLI or runtime changes since 0.1.3.

v0.1.3

Choose a tag to compare

@Karzone Karzone released this 29 Jul 15:08

Fixes MCP-server discovery. 0.1.2 shipped a .mcp/server.json using an outdated schema, which NuGet rejected as invalid ("server.json file is invalid") — so it wasn't a usable MCP server on NuGet or in Visual Studio. 0.1.3 rewrites the manifest to the current 2025-10-17 schema (registryType/identifier, transport: stdio, top-level version), so TestAtlas.Mcp is now a valid, discoverable MCP server. No CLI changes since 0.1.2.

v0.1.2

Choose a tag to compare

@Karzone Karzone released this 29 Jul 14:29

TestAtlas.Mcp is now a proper MCP-server package. It ships the McpServer NuGet package type and an embedded .mcp/server.json manifest, so it's discoverable in NuGet's MCP-server listing and Visual Studio's "Browse MCP servers" gallery — while remaining installable via dotnet tool install. The manifest version is auto-stamped from the package version so it can't drift.

CLI: index now accepts a folder (auto-discovers the single .sln/.csproj inside it) and returns actionable errors instead of a bare "input not found".

Docs: added a troubleshooting note for 401 Unauthorized installs behind corporate NuGet feeds.

v0.1.1

Choose a tag to compare

@Karzone Karzone released this 24 Jul 20:55
feat(mcp): ship as a NuGet MCP-server package with zero-arg map disco…

v0.1.0

Choose a tag to compare

@Karzone Karzone released this 24 Jul 20:19
ci: add Trusted Publishing (OIDC) workflow to publish both NuGet tools

Publishes TestAtlas.Cli and TestAtlas.Mcp to NuGet.org via GitHub Actions
using Trusted Publishing (NuGet/login OIDC) — no stored API key. Triggers
on a published GitHub Release or manual workflow_dispatch.