fanwei-e10-api-doc/evals/test-cases.md

fanwei-e10-api-doc Test Cases

Use this file to test trigger behavior and output quality.

Should trigger

1. 帮我写一份 E10 创建用车审批流程实例的接口文档。
2. 根据泛微 E10 流程字段生成外部系统调用文档。
3. 帮我整理 E10 OpenAPI 的 OAuth2 access_token 获取流程和请求示例。
4. 写一个 E10 工作流程创建实例接口文档，输出 Markdown。
5. 登录 E10 后帮我发现某个流程的表单字段，并生成接口说明。

Should not trigger

1. 帮我写一个普通 REST API 文档模板。
2. 解释一下 OAuth2 是什么。
3. 总结一下今天的会议纪要。
4. 帮我写非 E10 系统的接口文档。
5. 帮我修改 E10 表单字段配置。

Output quality checks

A generated external-facing document passes only if:

1. All example URLs use https://<E10_BASE>.
2. No credentials, cookies, tokens, app secrets, real IPs, or hostnames appear.
3. No internal /api/... management endpoint appears.
4. No database table names or column names appear.
5. OAuth2 code-to-token flow is included.
6. The document states that access_token is a request-body parameter, not a Bearer header.
7. Identity mapping is included for userType and deptType.
8. Workflow field tables use 字段名 | 类型 | 必填 | 说明.
9. Request examples use external identifiers such as job number and department code.
10. Missing requiredness or ambiguous mapping is marked 需确认.
11. No detail-table section appears when the workflow has no detail table.
12. Browser-harness, XHR interception, and UI navigation details do not appear in the final document.