Cli Anything Wiremock

作者 hkuds34f519533bc1無授權條款51K 個星標收錄於 2026年10月8日更新於 2026年10月8日儲存庫2 週前更新

Python CLI harness for WireMock HTTP mock server administration

AI 產生的概覽

用於透過 Admin REST API 管理 WireMock HTTP 模擬伺服器的命令列工具。

功能
此技能說明了一個包裝 WireMock Admin REST API 的命令列介面。它涵蓋用於管理樁對應、檢視已處理請求、控制具狀態情境、錄製真實後端流量以及讀取全域伺服器設定的命令群組,還包括頂層的狀態、重設與關閉命令。它可輸出供代理使用的 JSON,並支援透過環境變數設定連線。
適用情境
當代理或開發者需要在執行中的 WireMock 伺服器上設定、檢視或清理 HTTP 樁時使用。它適合整合測試驗證流程,例如計算請求次數、將請求與樁比對,以及錄製來自真實後端的流量。
執行需求
需要可連線的 WireMock 伺服器及其 Admin REST API;連線透過 WIREMOCK_HOST 與 WIREMOCK_PORT 環境變數設定。此技能不附帶指令碼,僅為說明文件。

Overview

cli-anything-wiremock is a command-line interface that wraps the WireMock Admin REST API (/__admin/). It allows agents and developers to manage HTTP stub mappings, inspect served requests, control stateful scenarios, and record real backend traffic — all from the terminal or from agent tool calls.

WireMock is commonly used in integration testing environments to replace real HTTP backends with controllable mock responses.

Command Groups

stub — Manage HTTP stub mappings

CommandDescription
stub listList all registered stubs
stub get <id>Get details of a specific stub by UUID
stub create <json>Create a stub from a JSON string
stub quick M URL SQuickly create a stub: METHOD URL STATUS_CODE
stub delete <id>Delete a stub by UUID
stub resetReset all stubs to the defaults on disk
stub savePersist in-memory stubs to disk
stub import <file>Import stubs from a JSON file

request — Inspect served requests

CommandDescription
request listList recent served requests
request find <pattern>Find requests matching a JSON pattern
request count <pattern>Count requests matching a JSON pattern
request unmatchedList requests that matched no stub (404s)
request resetClear the request journal

scenario — Stateful scenario management

CommandDescription
scenario listList all scenarios and current states
scenario set N SSet scenario NAME to STATE
scenario resetReset all scenarios to their initial state

record — Record traffic from a real backend

CommandDescription
record start <url>Start proxying + recording to TARGET_URL
record stopStop recording, return captured stubs
record statusCheck if currently recording
record snapshotSnapshot in-memory requests as stubs

settings — Global server settings

CommandDescription
settings getGet current global WireMock settings
settings versionShow WireMock server version

Top-level commands

CommandDescription
statusCheck if WireMock is running
resetFull reset: stubs + requests + scenarios
shutdownGracefully shut down the WireMock server

Key Examples

bash
# Check connectivitycli-anything-wiremock status
# Create a stub using quick formcli-anything-wiremock stub quick GET /api/users 200 --body '[{"id":1}]'
# Create a stub using full JSONcli-anything-wiremock stub create '{  "request": {"method": "POST", "url": "/api/orders"},  "response": {"status": 201, "body": "{\"id\":99}"}}'
# Verify a POST was made exactly oncecli-anything-wiremock --json request count '{"method":"POST","url":"/api/orders"}'# → {"count": 1}
# Scenario: advance statecli-anything-wiremock scenario set "cart-flow" "item-added"
# Record a real backendcli-anything-wiremock record start https://api.example.com# ... make requests ...cli-anything-wiremock record stop

Agent Guidance

Always use --json in agent contexts

Use --json for all invocations in scripts or agent tool calls. JSON output varies by command type (these are distinct response types, not an envelope wrapping all responses):

bash
# Data commands return raw WireMock API JSON directly:cli-anything-wiremock --json stub quick GET /api/hello 200 --body '{"hello":"world"}'# → {"id": "abc-123", "request": {...}, "response": {...}, ...}
cli-anything-wiremock --json stub list# → {"mappings": [...], "total": N}
# Void commands (delete, reset, save) return:# → {"status": "ok"}
# Errors return:# → {"status": "error", "message": "Connection refused"}

Connection via environment

Set connection params via environment variables before calling any command:

bash
export WIREMOCK_HOST=localhostexport WIREMOCK_PORT=8080

Workflow pattern for test verification

  1. Set up stubs before running the system under test:
    bash
    cli-anything-wiremock --json stub quick POST /api/payment 200 --body '{"success":true}'
  2. Run the system under test.
  3. Verify interactions:
    bash
    cli-anything-wiremock --json request count '{"method":"POST","url":"/api/payment"}'
  4. Clean up:
    bash
    cli-anything-wiremock reset

Error handling

Non-zero exit code on all errors. In --json mode, errors return {"status": "error", "message": "..."}. Success returns the raw WireMock API response.

來源與署名

來源:hkuds/cli-anything位於skills/cli-anything-wiremock提交34f5195

授權條款: 無授權條款

內容歸原作者所有。SourceWeft 從公開儲存庫中收錄這些內容。

檢舉或申請下架