シャドーイング練習: How to Write Test Cases for Manual Testing? - 動画で英語スピーキングを学ぶ
レッスンを作成中...
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.
✨ おすすめ動画
C11
245 文
QA Automation Interview Questions and Answers
Business EnglishInterview EnglishUniversity Students
C11
162 文
The Secret to Business Writing: Crash Course Business - Soft Skills #3
Business EnglishUniversity StudentsWorking Adults
C13
47 文
Seven Testing Principles: Software Testing
Business EnglishUniversity StudentsWorking Adults
C12
78 文
Why 95% of Android Developers Get Use Cases Wrong
Business EnglishUniversity StudentsWorking Adults
C12
32 文
How to Formulate Research Questions: From Ideas to Actionable Data
Business EnglishUniversity StudentsWorking Adults
C11
85 文
AI Can Write Code. And That’s the Problem.
Business EnglishUniversity StudentsWorking Adults
C141 文
🚨 Most organizations don't fail ISO/IEC 27001 because they don't understand the standard...
Business EnglishUniversity StudentsWorking Adults
C11
287 文
What is Quality Management? | Quality Management Tutorial | Invensis Learning
Business EnglishUniversity StudentsWorking Adults
C12
65 文
What Is REST API? Examples And How To Use It: Crash Course System Design #3
Business EnglishUniversity StudentsWorking Adults
C16
190 文
🔥Launching Analog VLSI Mastery : Cohort (0-100) || A Complete Placement Guide || Himanshu Agarwal
Business EnglishInterview EnglishUniversity Students
B21
98 文
I TESTED Passing Stats in eFootball
Business EnglishUniversity StudentsWorking Adults
C1204 文
Prompt Engineering - Guidelines
Business EnglishUniversity StudentsWorking Adults
マニュアルテストのテストケース作成についての動画の背景
この動画では、QAスペシャリストが扱うドキュメントの一つである「テストケース」について説明されています。テストケースとは、ソフトウェアの機能を検証するための一連のアクションの集合で、正しく動作するかどうかを確認したり、不具合を見つけたりするのに使われます。動画では、テストケースの種類や構成要素について詳しく解説されており、英語での技術用語や説明を聞くことで、英語スピーキング練習にも役立つ内容です。
日常会話に使えるトップ5フレーズ
- "QA specialists have to deal with different kinds of documentation."（QAスペシャリストはさまざまなドキュメントを扱わなければなりません）- 職業に関する説明で使えます。
- "A test case is a set of actions you execute to verify a particular software feature."（テストケースは、特定のソフトウェア機能を検証するために実行する一連のアクションです）- 用語の定義を説明するときに役立ちます。
- "Positive test cases use valid inputs to verify that software does what it is supposed to do."（ポジティブテストケースは、有効な入力を使ってソフトウェアが想定通りに動作するかを確認します）- 分類を説明する際のフレーズです。
- "Preconditions are a list of actions a user needs to perform before executing a test case."（前提条件は、テストケースを実行する前にユーザーが行う必要のあるアクションのリストです）- 手順の前に必要なことを説明するときに使えます。
- "Steps are the description of the actions required for verification."（ステップは、検証に必要なアクションの説明です）- 手順の内容を説明する際の基本フレーズです。
動画を使ったshadow speechのステップバイステップガイド
この動画は技術的な内容が多いため、shadow speechの練習には少し注意が必要です。まず、動画を1.25倍速で聞き、全体の流れを把握しましょう。次に、重要な用語（test case, positive, negative, destructiveなど）をメモし、発音を確認します。そして、1文ずつ止めて、同じ速さで繰り返します。特に、"a set of actions"や"verify a particular software feature"などのフレーズは、IELTSスピーキング対策にもなるので、発音とイントネーションを注意深く観察しましょう。YouTubeで英語学習する際は、このように技術系の動画も活用すると、専門用語の理解とスピーキングのスキルアップが同時にできます。最後に、自分でテストケースの説明を英語でまとめてみることで、練習の成果を確認しましょう。
この動画の文法
話し手がよく使っている文型を、動画の実際の表現とともに紹介します。
| 文型 | 動画での表現 |
|---|---|
| 受動態 be + 過去分詞 — 誰がするかより、何が起きるかに焦点を当てる | are created · is related · should be logged |
| 関係詞節 who / which + 節 — 人や物について情報を加える | those who are · person who does |
シャドーイングとは？英語上達に効果的な理由
シャドーイング（Shadowing）は、もともとプロの通訳者養成プログラムで開発された言語学習法で、多言語習得者として知られるDr. Alexander Arguelles によって広く普及されました。方法はシンプルですが非常に効果的：ネイティブスピーカーの英語を聞きながら、1〜2秒の遅延で声に出してすぐに繰り返す——まるで「影（shadow）」のように話者を追いかけます。文法ドリルや受動的なリスニングと異なり、シャドーイングは脳と口の筋肉が同時にリアルタイムで英語を処理・再現することを強制します。研究により、発音精度、抑揚、リズム、連音、リスニング力、そして会話の流暢さが大幅に向上することが確認されています。IELTSスピーキング対策や自然な英語コミュニケーションを目指す方に特におすすめです。