跟讀練習: How to Write Test Cases for Manual Testing? - 通過影片學習英語口語
選擇練習模式
每種模式都會開啟全屏練習室。
119 句
如果句子過短或過長，請點選 Edit 進行調整。
1
QA Madness.
2
How to write test cases for manual testing.
3
QA specialists have to deal with different kinds of documentation.
4
In today's video, I will tell you about one of such artifacts, a test case, what it is, and how to create one.
5
A test case is a set of actions you execute to verify a particular software feature or functionality.
6
Using test cases, we can make sure that a certain feature works as expected, or discover that it does not work properly.
7
There are three types of test cases.
8
Positive, negative, and destructive.
9
Positive test cases use valid inputs to verify that software does what it is supposed to do.
10
For example, when a user enters valid credentials, they can sign into the system.
11
Negative test cases use invalid inputs.
12
Their mission is to verify that the software does not do what it is not supposed to do.
13
For example, if a user enters an incorrect login or password, they cannot sign in.
14
Destructive test cases are created to learn what the system can handle until it breaks or destructs.
15
For this, a software tester can fast click on the sign in button to see what happens in this case.
16
Another example is a significant increase in web page load, it aims to check how many users a system can handle.
17
Like every document, a test case has a specific format.
18
It consists of eight elements, 1.
19
ID, 2.
20
Summary, 3.
21
Preconditions, 4.
22
Steps, 5.
23
Postconditions, 6.
24
Expected Results, 7.
25
Actual Results, 8.
26
Status.
27
Let's take a closer look at each of them.
28
Number 1.
29
ID.
30
As you can guess, it is the name of a test case.
31
An ID is a unique combination of letters and numbers.
32
As a rule, it is related to the project name, and indicates the number of a test case in the sequence.
33
For example, if we test a website called BuyOnline, you can name the first test case Bow1.
34
The second one will be Bow2, and so on.
35
Number 2.
36
Summary.
37
A summary is the main idea of a test case, a brief description of its contents.
38
For example, check adding a product to a wishlist.
39
Number 3.
40
Preconditions.
41
Preconditions are a list of actions a user needs to perform before executing a test case.
42
For example, a user should be logged in.
43
In this situation, you should include the credentials so a person working with this test case can reproduce it.
44
Preconditions are not mandatory, so you do not need to include this clause in every test case.
45
Number 4.
46
Steps.
47
Steps are the description of the actions required for verification.
48
Steps in a test case can go like this.
49
1. Open a website.
50
2. Open a product page.
51
3. Add a product to the wishlist.
52
Number 5.
53
Post conditions.
54
These are one or several actions that return the system to its original state.
55
For example, remove an item from the wishlist.
56
Just like preconditions, post conditions are not mandatory.
57
Number 6.
58
result.
59
It is what we expect to see getter achieve after the successful test case execution.
60
Back to our example, we expect to see a message about an item being added to a wishlist.
61
We also expect to find a product on the list after opening the corresponding section.
62
Number 7.
63
Actual result.
64
If there is a bug in the system, the actual result will differ from the expected one.
65
So, The actual result is what we get after the test case execution.
66
For example, the success message isn't displayed or the item doesn't appear on the wishlist.
67
Number 8.
68
Status.
69
It is the conclusion in your test case.
70
In this clause, you summarize the outcome in one word.
71
The most common statuses are success, failed, and blocked.
72
It depends on whether there are bugs in the software or not.
73
Keep in mind that test cases come in many different formats.
74
For example, sometimes you can use brief test cases with only four elements.
75
Summary, Priority, Steps, and Expected Result.
76
The sections can also have different names.
77
You can see software testers using the word inputs instead of steps, and outputs instead of results.
78
Moreover, you can find an alternative definition of post conditions.
79
Some use this term to describe the state of the system after test execution.
80
In this case, you may find it a bit complicated to tell the difference between post conditions and expected results.
81
To choose the correct format for the test case, you can look into the existing documentation or address other team members to specify this information.
82
The preferred format can depend on both a company's practices and the complexity of a tested feature.
83
Every test case should be comprehensive.
84
It should not depend on other test cases.
85
The description of the steps and expected results should be accurate and clear.
86
Make sure to include the necessary information, avoid vague formulations and excessive details.
87
All team members should be able to understand and execute a test case, even if they interact with software for the first time.
88
It should be easy to match a test case with the requirements in the product documentation.
89
All test cases should be repeatable.
90
In other words, a user should be able to reproduce a test case over and over again.
91
Finally, aim to create reusable test cases.
92
will help you to spend less time creating test documentation in the future.
93
There are several common mistakes QA engineers tend to make during test case writing.
94
The first is writing two abstract summaries.
95
The summary should be concise but specific.
96
For example, instead of the generalized check the wishlist functionality you can write check adding a product to the wishlist.
97
Another common mistake is interesting unclickable links.
98
When you insert a link in the text, make it active so another team member can click and open the intended page.
99
It is much more convenient than copying the text and pasting it in another tab.
100
And always make sure the link leads to the right page.
101
Providing two detailed explanations is not a good idea either.
102
Be specific, but not too specific.
103
There is no need to state the obvious through a very detailed description.
104
For example, it is enough to right-click the wishlist button.
105
Specifying
106
that it is the round blue wishlist button on the right
107
to the buy now button below the product description is not necessary.
108
Finally, the lack of details can also be confusing.
109
It is okay to be more specific when you add some tech directions.
110
It will be helpful for newbies or those who are not familiar yet with the technology you mentioned.
111
The example is on the screen.
112
So these are the basics of test case writing.
113
Let me finish this guideline with a tip.
114
To check how good your test case is, show it to a person who does not know anything about the project you are working on.
115
The questions you are going to hear will highlight the weak points of your test case.
116
You can find more examples of test cases in the article on our blog.
117
The link is in the description.
118
Subscribe to our channel to learn more about test documentation in the future.
119
See you in the next video.
FOR YOU
推薦影片
B230 句
7 Phases of Penetration Testing Explained | Think your system is safe? #cybersecurity #pentesting
Daily ConversationWorking Adults
B22
24 句
Reading Test 1 - Seccion 2 Good customer service in retail.
Daily ConversationWorking Adults
B21
227 句
How to Use Google Gemini Al (Full Tutorial)
Daily ConversationWorking Adults
B21
53 句
AQL Special Inspection Levels: How Do They Work?
Daily ConversationWorking Adults
B22
221 句
Testing the Burger King website | Exploratory Testing | QA
Daily ConversationWorking Adults
C12
43 句
SDLC Vs STLC: Software Development Life Cycle and Software Testing Life Cycle
Daily ConversationUniversity StudentsWorking Adults
B23
63 句
How To Land Your First Junior Dev Role
Daily ConversationUniversity StudentsWorking Adults
B23
163 句
The 2025 Step by Step Guide to PASSING your NEBOSH NG1/IG1 OBE Open Book Exam FIRST TIME!
Daily ConversationWorking Adults
B155
34 句
PART 1 TEST 4 EST 2026
Daily ConversationWorking Adults
B287 句
How to Remember Everything You Read
Daily ConversationWorking Adults
C12
65 句
What Is REST API? Examples And How To Use It: Crash Course System Design #3
Daily ConversationUniversity StudentsWorking Adults
C12
236 句
The 7 Quality Control (QC) Tools Explained with an Example!
Daily ConversationUniversity StudentsWorking Adults
本節課你將練習什麼？
通過本節課，你將跟隨影片學習“如何編寫手動測試用例”，同時練習英語聽力與口語表達。你會了解測試用例的型別、結構等專業知識，還能通過影子跟讀法（shadowspeak）模仿影片中的語音語調，提升英語發音和口語流暢度。
核心詞彙與短語
- test case：測試用例
- manual testing：手動測試
- positive test case：正向測試用例
- negative test case：反向測試用例
- preconditions：前置條件
- expected results：預期結果
影子跟讀法練習技巧
影片語速適中，語調清晰，非常適合影子跟讀法（shadow speak）練習。建議你先完整聽一遍，熟悉內容後，嘗試滯後1-2秒跟讀。注意模仿說話人的重音和停頓，比如“QA specialists have to deal with different kinds of documentation”中，“QA specialists”和“documentation”需要重讀。練習時，重點關注“test case”“preconditions”等專業術語的發音，這能有效提高英語發音的準確性。此外，你還可以將影片分成小段，逐句跟讀，對比自己與原音的差異，反覆調整。堅持使用影子跟讀法（shadowspeaks），你的口語流暢度和聽力理解能力都會顯著提升。快跟著影片試一試吧！
影片中的語法
說話人最常用的結構，並附上影片中的原話：
| 結構 | 影片中的用法 |
|---|---|
| 被動語態 be + 過去分詞 — 強調發生了什麼，而不是誰做的 | are created · should be logged · being added |
| 定語從句 who / which + 從句 — 補充說明人或事物 | those who are · person who does |
什麼是跟讀法？
跟讀法 (Shadowing) 是一種有科學依據的語言學習技巧，最初開發用於專業口譯員的培訓，並由多語言者Alexander Arguelles博士普及。這個方法簡單而強大：您在聽英語母語原聲的同時立即大聲重複——就像是一個延遲1-2秒緊跟說話者的影子。與被動聽力或語法練習不同，跟讀法強迫您的大腦和口腔肌肉同時處理並模模擬實的講話模式。研究表明它能顯著提高發音準確性，語調，節奏，連讀，聽力理解和口語流利度——使其成為雅思口語備考和真實英語交流最有效的方法之一。