跟读练习: 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.

這個影片適合誰?

無論你是想提升「英語影子跟读」技巧的初學者,還是想通過「看YouTube學英語」練習口語的中級學員,這部講解軟件測試原則的影片都很合適。它的對話邏輯清晰,用詞貼近日常,既能學到專業術語,又能鍛煉「英语口语练习」中的連貫表達,非常適合當作shadowing素材。

值得學的詞彙和短語

  • exhaustive testing:徹底測試。影片中提到「窮盡測試不可能實現」,這個短語常用於技術場景。
  • Pesticide Paradox:農藥悖論。指重複測試會導致測試用例失效,類比有趣,容易記憶。
  • drive home this point:強調這一點。口語中用來加強論述,比如「用例子來drive home this point」。

如何練好口音?

這位講者的發音清晰,語速中等,很適合shadowing。練習時注意以下兩點:一是重讀關鍵詞,比如「defects」「risk assessment」等專業詞彙要讀得稍重,突出語義重點;二是模仿語調起伏,講者在解釋複雜概念時(如「5的15次方組合」)會輕微升調,表達疑問或強調時降調,跟讀時要貼合這種節奏。建議打開影片,逐句進行「影子跟读」,反覆練習直到語速和語調接近原聲,這對提升口語流暢度幫助很大。

想找更多適合的shadowing site?不妨從這類知識型YouTube影片入手,既能學英語,又能長見識,一舉兩得!

什么是跟读法?

跟读法 (Shadowing) 是一种有科学依据的语言学习技巧,最初开发用于专业口译员的培训,并由多语言者Alexander Arguelles博士普及。这个方法简单而强大:您在听英语母语原声的同时立即大声重复——就像是一个延迟1-2秒紧跟说话者的影子。与被动听力或语法练习不同,跟读法强迫您的大脑和口腔肌肉同时处理并模仿真实的讲话模式。研究表明它能显着提高发音准确性,语调,节奏,连读,听力理解和口语流利度——使其成为雅思口语备考和真实英语交流最有效的方法之一。

影子跟读法: 阅读完整分步指南 →