test-chapter
Skill0 starsChanged 21 days agoMITView on GitHub
毕设论文系统测试章节（测试环境、功能测试用例表、非功能测试、测试结论），并可据此真实执行测试。写第 6 章系统测试或设计测试用例时使用。
In this repository6 other files it gives its agents.
- code-to-thesisSkill
- defense-prepSkill
- requirements-analysisSkill
- system-designSkill
- thesis-proposalSkill
- thesis-writingSkill
The file
Files
系统测试章节
结构
- 测试目的与方法：黑盒功能测试为主，可补充接口测试（Postman/curl/自动化测试）、兼容性测试。
- 测试环境：表格列出操作系统、浏览器/微信版本、Node/JDK 版本、数据库版本——写用户实际的环境，不清楚就问。
- 功能测试用例：每个核心模块一张表：
| 用例编号 | 测试项 | 前置条件 | 操作步骤 | 输入数据 | 预期结果 | 实际结果 | 结论 |
| TC-LOGIN-01 | 正确登录 | 账号已存在 | 输入账号密码点登录 | admin / 正确密码 | 进入首页 |
- 每个模块覆盖：正常流程、必填为空、格式错误、边界值（最长/最大）、权限（普通用户访问管理接口）、重复提交。
- 「实际结果」「结论」两列必须来自真实执行。先生成用例让用户逐条执行，或在用户同意后用项目自带测试/接口脚本跑，再填结果；没跑过的留空，不能直接写「通过」。
- 非功能测试：如用浏览器开发者工具或压测工具测接口响应时间，写清工具、并发数、测得数值；没测就不写数值。
- 测试结论：发现了哪些缺陷、如何修复、最终是否满足需求分析中的目标。写出真实发现并修复的问题反而更可信。
常见问题
- 用例只写「点击按钮，成功」→ 要写具体输入和可观察的预期结果。
- 所有用例都通过且零缺陷 → 不真实，老师会追问。
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.