Repository navigation
feat(test-feature): use the Doable MCP result tools (0.2.17) - #39
Merged
Merged
Conversation
…nd test generation move to the web app (0.2.17) The Doable MCP server replaced its suite, generation and run tools with result tools. doable-test-feature now names them: list_test_suites to find a suite, get_test_spec and list_test_cases to inspect it, run_test_cases and get_run (wait_seconds=60) to run test cases, and get_test_case to read why one did not pass. The MCP no longer creates suites or generates test cases, so the skill asks the developer to do those in the Doable web app and waits for the test cases. It reads Incomplete as no evidence about the code. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The Doable MCP server replaced its suite, generation and run tools with result tools (getdoable/doable-mcp#27).
doable-test-featurenow names them:list_test_suites(querymatches name or entry URL). If none matches, the developer creates one in the Doable web app; the MCP no longer creates suites.get_test_specandlist_test_cases.get_test_spec(wait=true).list_test_cases, runs withrun_test_cases, waits withget_run(wait_seconds=60), and reads each test case that did not pass withget_test_case.Incompleteis no evidence about the code.web_url.The Code Context steps and the other skills do not change. Version 0.2.17 (CHANGELOG, manifests, helper client version, release check).
Compatibility
Merge after getdoable/doable-mcp#27 is deployed. Installed 0.2.16 copies say only "use Doable MCP" for these steps, so against the new server their agent finds the result tools by itself; it cannot create suites or generate cases, which now happen in the web app.
Tests
npm test: 6 passed, release and workflow checks pass.🤖 Generated with Claude Code