test(@angular/cli): add initial e2e test for MCP server tool registration #30803
Conversation
02653ec to
6423c66
Compare
| '--no', | ||
| '@angular/cli', | ||
| 'mcp', | ||
| ...args, |
There was a problem hiding this comment.
Question: How is npx pulling in the locally built version of the CLI? Is this going through Verdaccio through an .npmrc configuration or something like that?
I'm wondering if there's a more direct implementation through something like: mcp-inspector-cli --cli node_modules/.bin/ng mcp ...args?
There was a problem hiding this comment.
npx uses the locally installed version if present, then the global. If neither are present, it then tries to download from the registry. However, the --no option prevents that last step. The package should always be present so the failure with the --no option effectively acts as an assertion for the test setup.
The arguments are based on the recommended usage/configuration as well to better represent real world use.
…tion Introduces the first end-to-end test for the MCP server. The new test, `registers-tools.ts`, verifies that the MCP server correctly initializes and registers its default set of tools. This provides a foundation for more comprehensive e2e testing of the MCP server and its features.
6423c66 to
469ff77
Compare
Introduces the first end-to-end test for the MCP server. The new test,
registers-tools.ts, verifies that the MCP server correctly initializes and registers its default set of tools. This provides a foundation for more comprehensive e2e testing of the MCP server and its features.