Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →laolaoshiren/api-tester
依据真实 OpenAPI、路由实现和现有测试生成并验证 API 测试。用于用户要求测试接口、补集成测试、验证 API 契约、生成回归用例或排查接口兼容性时；区分“生成测试”和“执行请求”的授权，不猜测状态码、响应结构或 SLA，不在未确认环境中发送写请求。
Passed 18 of 21 test cases with the skill, and 16 of 21 without it.
and 4 more in the full report
4 fixed15 passed either way1 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 4 test cases the skill fixed. Same model, same prompt, with and without the skill.
在为 `PUT /api/v1/users/{id}` 编写测试时，我发现 Swagger 规范中写着 `email` 字段是必填项，但最新的 Go Controller 代码里 `email` 被标记为 `omitempty` 并且逻辑允许留空。我应该直接修改单元测试断言接口允许留空，还是修改 Swagger 说明？
| Checked | Without skill | With skill |
|---|---|---|
| The response instructs to document the contract discrepancy and request user confirmation instead of baking in guesses. | Missed | Passed |
| The response advises against arbitrarily editing production code or contract specs to pass the test. | Missed | Passed |
The instructions your model reads when the skill loads.
先读取适用的仓库规则、测试说明、Git 状态和项目脚本，再按实际存在情况检查：
记录规范、实现与现有测试之间的不一致。无法确定哪个行为才是期望契约时，列出证据并请求确认，不用新测试固化猜测。
为目标 endpoint 记录：
| 项目 | 证据 |
|---|---|
| method 与 path | OpenAPI 或路由位置 |
| 认证与权限 | security scheme、中间件或调用方 |
| 请求参数与约束 | Schema、DTO 或验证器 |
| 已声明响应 | 状态码、响应结构与 header |
| 副作用与幂等性 | 实现、文档或调用链 |
| 测试环境与清理 | fixture、事务或 teardown |
不要默认每个接口都应返回 400、401、403、404、422 或 500。只有契约已声明或代码路径真实可达时才生成对应断言。
在执行任何请求前确认：
test cases passed, vs 16 / 21 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.