@slbdn/mcp-tester 1.5.3 → 1.5.4
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +5 -0
- package/README.md +29 -26
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -7,6 +7,11 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
|
|
|
7
7
|
|
|
8
8
|
## [Unreleased]
|
|
9
9
|
|
|
10
|
+
## [1.5.4] - 2026-10-08
|
|
11
|
+
|
|
12
|
+
### Fixed
|
|
13
|
+
- Rebuilt the README architecture diagram. Its box borders were misaligned (right edges varied by up to six columns, so the boxes did not line up), and the `MCP Server (child process)` label was wrong for the HTTP/SSE transports, which connect to a remote server rather than spawning a process. The diagram now has consistently aligned borders and shows the tested capabilities (`Tools`, `Resources`, `Prompts`, `Sampling`, `Elicitation`, `Notifications`).
|
|
14
|
+
|
|
10
15
|
## [1.5.3] - 2026-10-08
|
|
11
16
|
|
|
12
17
|
### Fixed
|
package/README.md
CHANGED
|
@@ -32,32 +32,35 @@ No more manual clicking through inspectors — write real tests, run them in CI,
|
|
|
32
32
|
## Architecture
|
|
33
33
|
|
|
34
34
|
```
|
|
35
|
-
|
|
36
|
-
│
|
|
37
|
-
│
|
|
38
|
-
│
|
|
39
|
-
│
|
|
40
|
-
│
|
|
41
|
-
│
|
|
42
|
-
│
|
|
43
|
-
│ │
|
|
44
|
-
│ │
|
|
45
|
-
│ │
|
|
46
|
-
│ │
|
|
47
|
-
│ │
|
|
48
|
-
│ │
|
|
49
|
-
│ │
|
|
50
|
-
│ │
|
|
51
|
-
│ │
|
|
52
|
-
│
|
|
53
|
-
│
|
|
54
|
-
│
|
|
55
|
-
│ │
|
|
56
|
-
│ │
|
|
57
|
-
│ │
|
|
58
|
-
│ │
|
|
59
|
-
│
|
|
60
|
-
|
|
35
|
+
┌──────────────────────────────────────────────────────────────────────┐
|
|
36
|
+
│ Your Test Suite │
|
|
37
|
+
│ ┌──────────┐ ┌───────────┐ ┌────────┐ ┌───────────────────┐ │
|
|
38
|
+
│ │ Jest │ │ Vitest │ │ assert │ │ Custom Runner │ │
|
|
39
|
+
│ │ matchers │ │ matchers │ │ module │ │ (any framework) │ │
|
|
40
|
+
│ └────┬─────┘ └─────┬─────┘ └───┬────┘ └────────┬──────────┘ │
|
|
41
|
+
│ │ │ │ │ │
|
|
42
|
+
│ ┌──────▼──────────────▼────────────▼────────────────▼────────────┐ │
|
|
43
|
+
│ │ MCPClient │ │
|
|
44
|
+
│ │ ┌────────────────────────────────────────────────────────┐ │ │
|
|
45
|
+
│ │ │ start() │ stop() │ listTools() │ callTool() │ ... │ │ │
|
|
46
|
+
│ │ └───────────────────────────┬────────────────────────────┘ │ │
|
|
47
|
+
│ │ │ │ │
|
|
48
|
+
│ │ ┌───────────────────────────▼────────────────────────────┐ │ │
|
|
49
|
+
│ │ │ Retry │ Timeout │ Error Handling │ │ │
|
|
50
|
+
│ │ │ MCPTimeoutError │ MCPConnectionError │ ... │ │ │
|
|
51
|
+
│ │ └───────────────────────────┬────────────────────────────┘ │ │
|
|
52
|
+
│ └───────────────────────────────┼────────────────────────────────┘ │
|
|
53
|
+
│ │ stdio, HTTP, SSE │
|
|
54
|
+
│ ┌───────────────────────────────▼────────────────────────────────┐ │
|
|
55
|
+
│ │ MCP Server │ │
|
|
56
|
+
│ │ ┌──────────────┐ ┌──────────────┐ ┌──────────────┐ │ │
|
|
57
|
+
│ │ │ Tools │ │ Resources │ │ Prompts │ │ │
|
|
58
|
+
│ │ └──────────────┘ └──────────────┘ └──────────────┘ │ │
|
|
59
|
+
│ │ ┌──────────────┐ ┌──────────────┐ ┌──────────────┐ │ │
|
|
60
|
+
│ │ │ Sampling │ │ Elicitation │ │Notifications │ │ │
|
|
61
|
+
│ │ └──────────────┘ └──────────────┘ └──────────────┘ │ │
|
|
62
|
+
│ └────────────────────────────────────────────────────────────────┘ │
|
|
63
|
+
└──────────────────────────────────────────────────────────────────────┘
|
|
61
64
|
```
|
|
62
65
|
|
|
63
66
|
**Data flow**: Your test calls `MCPClient` → which sends JSON-RPC over stdio/HTTP/SSE → to the MCP server → server responds → `MCPClient` returns typed results → your assertion validates them.
|