Day 04 - Reading Requirements and Technical Documentation

今日目标

能从英文需求、API 文档、设计文档里提取测试相关信息。

30 分钟学习安排

时间	模块	做什么
0-5 分钟	核心词汇	读词汇、短语和中文含义，重点记能直接在 QA 场景复用的表达。
5-12 分钟	阅读/听力输入	阅读当天短文；第二遍当听力材料朗读或用 TTS 播放，只抓问题、证据、动作、结论。
12-18 分钟	句型拆解	把长句拆成可替换模板，换成自己的工作内容。
18-25 分钟	口语输出	完成 60-120 秒英文表达，必须录音。
25-30 分钟	复盘	标记卡住的词、句子和下一次要改进的一点。

核心词汇

English	中文	QA 场景用法
requirement	需求	Use it when you describe requirement in a defect, test plan, review, meeting, or interview.
specification	规格说明	Use it when you describe specification in a defect, test plan, review, meeting, or interview.
constraint	约束	Use it when you describe constraint in a defect, test plan, review, meeting, or interview.
assumption	假设	Use it when you describe assumption in a defect, test plan, review, meeting, or interview.
required field	必填字段	Use it when you describe required field in a defect, test plan, review, meeting, or interview.
optional field	可选字段	Use it when you describe optional field in a defect, test plan, review, meeting, or interview.
precondition	前置条件	Use it when you describe precondition in a defect, test plan, review, meeting, or interview.
acceptance criteria	验收标准	Use it when you describe acceptance criteria in a defect, test plan, review, meeting, or interview.
error scenario	错误场景	Use it when you describe error scenario in a defect, test plan, review, meeting, or interview.
permission	权限	Use it when you describe permission in a defect, test plan, review, meeting, or interview.
configuration	配置	Use it when you describe configuration in a defect, test plan, review, meeting, or interview.
compatibility	兼容性	Use it when you describe compatibility in a defect, test plan, review, meeting, or interview.

高频短语

from a QA perspective
validate the expected behavior
cover the edge cases
reduce regression risk
collect enough evidence
clarify the acceptance criteria
prioritize the critical path
follow up with a verification note

阅读 / 听力材料

先慢读一遍，再用正常语速朗读一遍。不要逐字翻译，重点抓 problem -> evidence -> action -> result。

You read a requirement that says users can cancel an order within 30 minutes. You identify the time boundary, payment status dependency, permission rule, and error cases that need tests. The most important point is not just to say that something is broken, but to explain why it matters, who may be affected, and how the team can gain confidence before release. A strong QA explanation is specific, evidence-based, and calm. It connects user impact with technical details, and it gives the team a clear next step.

理解检查

What is the quality risk in this scenario?
What evidence would you collect as a QA engineer?
What should be tested first if time is limited?
How would you explain the issue to a developer or product manager?

句型拆解

The issue happens when...
The expected result is..., but the actual result is...
I verified this by...
From a QA perspective, the risk is...
The next step is to...

可直接替换的输出模板

Today I want to talk about reading requirements and technical documentation.
The context is that we need to protect the user experience and reduce release risk.
From a QA perspective, the key risk is [risk].
The evidence I would collect includes [logs / screenshots / test data / metrics].
My suggested next step is to [action].
This gives the team more confidence because [reason].

示范口语稿

这一段先照读，再改成你的真实项目。

In this situation, I would first describe the behavior in a simple and testable way. You read a requirement that says users can cancel an order within 30 minutes. From a QA perspective, I need to make the expected result and the actual result very clear. Then I would add reproduction steps, environment information, and any logs or screenshots that help the developer investigate the issue. After the fix is ready, I would verify the original scenario first, then run a small regression check around the related flow. My goal is to help the team understand the risk quickly and avoid the same problem in the next release.

追问练习

Can you give one concrete example from your own work?
What would you test first if the release were tomorrow?
What evidence would make your explanation more convincing?

跟读训练

I found a quality risk in this scenario.
The expected behavior is clear, but the edge cases are not covered yet.
I verified the fix with test data, logs, and regression checks.
My recommendation is to test the critical path first and expand coverage after that.
I can follow up with a short verification note after the meeting.

口语任务

录一段 60-120 秒英文。必须包含以下 5 点：

context
quality risk
evidence
action
next step or result

QA 角色强化

不要只说 “I tested it”。说清楚你测了什么、为什么优先测、用了什么证据。
把 developer 视角和 user impact 连接起来：这个缺陷会影响谁，影响多大，为什么需要现在处理。
练习把“感觉有风险”改成可讨论的英文证据：logs, reproduction steps, affected flow, severity, release criteria。

AI 时代扩展：Testing Agents / Skills / MCP

新增词汇

English	中文
AI-assisted testing	AI 辅助测试
test agent	测试 agent
agent workflow	agent 工作流
human-in-the-loop	人工把关
LLM evaluation / eval	大模型评估
tool calling	工具调用
MCP server	MCP 服务器
skill	可复用技能/流程能力
prompt injection	提示注入
hallucination	幻觉
false confidence	虚假信心
ground truth	标准答案/真实依据

QA 新场景

Use AI as a practice partner or assistant, but keep the QA conclusion evidence-based.

表达重点

基础周只需要会说 AI-assisted testing, test agent, human-in-the-loop。不要一开始堆概念，先把缺陷、测试、站会和文档表达说清楚。

可复用表达

I used an AI assistant to draft the test ideas, but I verified the result with real steps, logs, and expected behavior.

追问加练

Which part can AI help with?
Which part must still be verified by a human QA?
What evidence prevents false confidence?

今日作业

录音 1-3 分钟，先看稿读一遍，再只看关键词复述一遍。
把今天的模板替换成你真实工作中的项目、缺陷、接口或测试任务。
整理 8 个你能在工作会议或面试里复用的表达。
写一版 80-150 词英文稿，明天开始前先复述一次。

自检清单

我能不用中文解释今天主题。
我能说出至少 8 个核心词汇。
我能把模板替换成自己的真实 QA 工作内容。
我的录音里有明确的风险、证据和下一步。
我知道明天要重复练哪一句。