返回提示词库Back to prompts
语言当前显示中英对照
写作表达writing
FAT Test Plan Writer
来自 prompts.chat 开放提示词库的公开模板，适合写作、改写和表达。正文保留原文，方便直接复制使用。
An open prompt template from prompts.chat for writing, rewriting, and communication. The original wording is preserved for direct copying.
ChatGPTClaudeGemini
0 次复制copies·小黑丸整理Curated by XHW
提示词正文Prompt text
I want you to act as a commissioning engineer writing a Factory Acceptance Test (FAT) plan. Machine: ${Machine description:a sorting conveyor with three diverters}. Below is the functional specification, numbered by clause.
Write test cases as a table:
Test ID | Spec clause | Precondition | Action (what I do or force) | Expected result (exact tags, values, HMI text and timing) | Pass/Fail | Witness
Cover, for every clause:
1. Normal operation: start, run, stop, mode changes.
2. Each sensor stuck on, stuck off and flickering. Each actuator failing to move.
3. Faults during stop and during reset. Two faults at once.
4. Power cycle, controller stop/run and communication loss: what must restart, what must not.
5. Boundary values: test just under and just over every timer and setpoint in the spec.
Where the spec does not define the reaction, write NOT IN SPEC and add a question. Do not invent behaviour.
After the table give: a clause-to-test coverage matrix (any clause with no test is a gap), and the order to run the tests so I force and clear signals the fewest times.
=== FUNCTIONAL SPECIFICATION ===
${Paste spec}I want you to act as a commissioning engineer writing a Factory Acceptance Test (FAT) plan. Machine: ${Machine description:a sorting conveyor with three diverters}. Below is the functional specification, numbered by clause.
Write test cases as a table:
Test ID | Spec clause | Precondition | Action (what I do or force) | Expected result (exact tags, values, HMI text and timing) | Pass/Fail | Witness
Cover, for every clause:
1. Normal operation: start, run, stop, mode changes.
2. Each sensor stuck on, stuck off and flickering. Each actuator failing to move.
3. Faults during stop and during reset. Two faults at once.
4. Power cycle, controller stop/run and communication loss: what must restart, what must not.
5. Boundary values: test just under and just over every timer and setpoint in the spec.
Where the spec does not define the reaction, write NOT IN SPEC and add a question. Do not invent behaviour.
After the table give: a clause-to-test coverage matrix (any clause with no test is a gap), and the order to run the tests so I force and clear signals the fewest times.
=== FUNCTIONAL SPECIFICATION ===
${Paste spec}使用场景Best used for
适合写作、改写和表达，使用前请替换其中的角色、主题和具体约束。
Useful for writing, rewriting, and communication. Replace the role, topic, and constraints before using it.
使用提醒Usage note
这条内容来自 prompts.chat 公开提示词库；说明为中英对照，正文保留来源原文。使用前请检查并按自己的工作场景改写。
Sourced from the prompts.chat public library. Descriptions are bilingual; the prompt preserves the original text. Review and adapt it to your work before use.