You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Contains fixes for https://github.com/apollographql/apollo-mcp-server/issues/327
14
+
15
+
The validate tool was parsing the operation passed in to it against the schema but it wasn't performing the validate function on the ExecutableDocument returned by the Parser. This led to cases where missing required arguments were not caught by the Tool.
16
+
17
+
This change also updates the input schema to the execute tool to make it more clear to the LLM that it needs to provide a valid JSON object
18
+
19
+
## 🛠 Maintenance
20
+
21
+
### test: adding a basic manual e2e test for mcp server - @alocay PR #320
22
+
23
+
Adding some basic e2e tests using [mcp-server-tester](https://github.com/steviec/mcp-server-tester). Currently, the tool does not always exit (ctrl+c is sometimes needed) so this should be run manually.
24
+
25
+
### How to run tests?
26
+
Added a script `run_tests.sh` (may need to run `chmod +x` to run it) to run tests. Basic usage found via `./run_tests.sh -h`. The script does the following:
27
+
28
+
1. Builds test/config yaml paths and verifies the files exist.
29
+
2. Checks if release `apollo-mcp-server` binary exists. If not, it builds the binary via `cargo build --release`.
30
+
3. Reads in the template file (used by `mcp-server-tester`) and replaces all `<test-dir>` placeholders with the test directory value. Generates this test server config file and places it in a temp location.
31
+
4. Invokes the `mcp-server-tester` via `npx`.
32
+
5. On script exit the generated config is cleaned up.
33
+
34
+
### Example run:
35
+
To run the tests for `local-operations` simply run `./run_tests.sh local-operations`
36
+
37
+
### Update snapshot format - @DaleSeo PR #313
38
+
39
+
Updates all inline snapshots in the codebase to ensure they are consistent with the latest insta format.
40
+
41
+
### Hardcoded version strings in tests - @DaleSeo PR #305
42
+
43
+
The GraphQL tests have hardcoded version strings that we need to update manually each time we release a new version. Since this isn't included in the release checklist, it's easy to miss it and only notice the test failures later.
0 commit comments