シャドーイング練習: Seven Testing Principles: Software Testing - 動画で英語スピーキングを学ぶ
レッスンを作成中...
1
Consider a scenario where you are moving a file from folder A to folder B.
2
Think of all the possible ways you can test this.
3
Pause the tutorial and think over the exercise.
4
Apart from the usual scenarios, you can also test the following conditions.
5
trying to move the file when it is open.
6
You do not have the security rights to paste the file in folder B.
7
Folder B is on a shared drive and storage capacity is full.
8
Folder B already has a file with the same name.
9
In fact, the list is endless.
10
Or suppose you have 15 input fields to test, each having 5 possible values.
11
The number of combinations to be tested would be 5 raised to 15.
12
If you were to test all the possible combinations, project execution time and costs will rise exponentially.
13
Hence, one of the testing principles states that exhaustive testing is not possible.
14
Instead, we need the optimal amount of testing based on the risk assessment of the application.
15
And the million dollar question is, how do you determine this risk?
16
To answer this, let's do an exercise.
17
In your opinion, which operation is most likely to cause your operating system to fail?
18
I'm sure most of you would have guessed opening 10 heavy graphics applications all at the same time.
19
So if you were testing this operating system, you would realize that defects are likely to be found in a multitasking module, and that needs to be tested thoroughly.
20
Which brings us to our next principle, Defect Clustering, which states that a small number of modules contain most of the defects detected.
21
With experience you can identify such risky modules.
22
But this approach has its own problems.
23
If the same tests are repeated over and over again, eventually the same test cases will no longer find new bugs.
24
This is another principle of testing called pesticide paradox.
25
To overcome this, the test cases need to be regularly reviewed and revised, adding new and different test cases to help find more defects.
26
But even after all this sweat and hard work in testing, you can never claim your product is bug-free.
27
To drive home this point, let's see this video of the public launch of Windows 98.
28
Let's plug it in.
29
It's going to say, hey, I see you plugged in a new device, and it's going to load in the appropriate drivers.
30
You'll notice that this scanner build Whoa.
31
Moving right along.
32
That must be why we're not shipping Windows 98 yet.
33
You would think a company like Microsoft would have tested their OS thoroughly
34
and would not risk their reputation just to see their OS crashing during its public launch.
35
Hence, the testing principle states that testing shows the presence of defects.
36
Testing reduces the probability of undiscovered defects remaining in the software.
37
But even if no defects are found, it is not a proof of correctness or a proof that no defects remain in the system.
38
But what if you work extra hard, taking all precaution and making sure your software product is 99% bug-free
39
and the software does not meet the needs and requirements of the client?
40
Which leads us to our next principle, which states that absence of error is a fallacy.
41
Finding and fixing defects does not help if the system build is unusable and does not fulfill the user's needs and requirements.
42
To fix this problem, the next principle of testing, early testing, states that testing should start as early as possible in the software development lifecycle,
43
so that any defects in the requirements or design phase are captured as well.
44
We'll have more on this principle in a later tutorial.
45
And the last principle of testing states that the testing is context dependent, which basically means
46
that the way you test an e-commerce site will be different from the way you test a commercial off-the-shelf application.
47
Before we close this tutorial, here's a quick recap of the seven testing principles.
📺 同じチャンネル
✨ おすすめ動画
C130 文
7 Phases of Penetration Testing Explained | Think your system is safe? #cybersecurity #pentesting
Business EnglishUniversity StudentsWorking Adults
C11
126 文
How I use AI as a senior software engineer and 5 principles of AI explained in 10 minutes
Business EnglishUniversity StudentsWorking Adults
C12
119 文
How to Write Test Cases for Manual Testing?
Business EnglishUniversity StudentsWorking Adults
C11
111 文
Financial Analysis Fundamentals: How to Analyze Financial Statements Like a Pro Part 7 | CFI Course
Business EnglishUniversity StudentsWorking Adults
C15
188 文
Fix your Trousers Fitting Issues | Body Specific Adjustments (Part 1)
Business EnglishUniversity StudentsWorking Adults
C12
82 文
CAP Theorem Simplified
Business EnglishUniversity StudentsWorking Adults
C12
236 文
The 7 Quality Control (QC) Tools Explained with an Example!
Business EnglishUniversity StudentsWorking Adults
C1240 文
PMBOK 8th Edition Practice Questions 1 - 10 - Pass your PMP and Learn the PMBOK Guide
Business EnglishUniversity StudentsWorking Adults
C11
96 文
Design Patterns in Java Theory
Business EnglishUniversity StudentsWorking Adults
C13
56 文
What is SMT (Surface Mount Technology)? PCB Assembly (Part 3)
Business EnglishUniversity StudentsWorking Adults
C1105 文
100+ Docker Concepts you Need to Know
American AccentBusiness EnglishUniversity StudentsWorking Adults
ソフトウェアテストの原則を学ぶなら、実生活のシナリオで考えよう
ビデオでは、ファイルをフォルダAからBに移動するという簡単な作業を例に、テストの考え方を説明しています。実はこれは日常の英語学習にも似ています。例えば、「shadowspeak」の練習では、単語やフレーズを自然に使うために、さまざまな「状況」を想定して練習する必要があります。ソフトウェアテストが「すべての組み合わせを試すのは不可能」と言うように、英語スピーキング練習も「完璧な状態」を目指すのではなく、リスク（間違いやすい箇所）を見極めて重点的に取り組むことが大切です。
覚えておきたい便利なフレーズやコロケーション
- exhaustive testing：徹底的なテスト（「exhaustive」は「徹底的な」という意味で、IELTS スピーキング対策でも「徹底的な練習」を表すのに使えます）
- risk assessment：リスク評価（「assessment」は「評価」で、「リスクを評価する」というフレーズはビジネス英語や日常会話でも頻出）
- defect clustering：欠陥の集中（「clustering」は「集中すること」で、「問題が集中する箇所」を表すのに便利）
- Pesticide Paradox：農薬パラドックス（テストケースを繰り返し使うと新しいバグが見つからなくなる現象を指し、英語で説明する際のキーワード）
さあ、shadow speechのチャレンジを始めよう！
今すぐできる練習は、ビデオの一部を選んで「shadowing」を行うことです。例えば、「testing shows the presence of defects」という文を聞きながら、1秒遅れで繰り返しましょう。声のトーンやリズム、イントネーションまで真似ることで、自然な発音と流暢さが身につきます。特にIELTS スピーキング対策では、この方法が効果的です。また、「defect clustering」の説明部分を使って、自分の言葉で要約してみるのも良いでしょう。これで、英語での思考力と表現力が向上します。
ソフトウェアテストの原則は、英語学習にも応用できる考え方がたくさんあります。「shadow speak」の練習では、「早期テスト」の原則のように、早い段階から間違いを見つけて修正することが大切です。毎日少しずつ取り組むことで、確実にスキルが上達しますよ！
シャドーイングとは？英語上達に効果的な理由
シャドーイング（Shadowing）は、もともとプロの通訳者養成プログラムで開発された言語学習法で、多言語習得者として知られるDr. Alexander Arguelles によって広く普及されました。方法はシンプルですが非常に効果的：ネイティブスピーカーの英語を聞きながら、1〜2秒の遅延で声に出してすぐに繰り返す——まるで「影（shadow）」のように話者を追いかけます。文法ドリルや受動的なリスニングと異なり、シャドーイングは脳と口の筋肉が同時にリアルタイムで英語を処理・再現することを強制します。研究により、発音精度、抑揚、リズム、連音、リスニング力、そして会話の流暢さが大幅に向上することが確認されています。IELTSスピーキング対策や自然な英語コミュニケーションを目指す方に特におすすめです。