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 从公开仓库中收录这些内容。

举报或申请下架