쉐도잉 연습: 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
236 문장
The 7 Quality Control (QC) Tools Explained with an Example!
Business EnglishUniversity StudentsWorking Adults
C12
82 문장
CAP Theorem Simplified
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
이번 수업에서 배울 내용
이번에는 소프트웨어 테스팅의 7가지 원칙에 대해 설명하는 유튜브 영어 공부 영상을 통해 영어 듣기와 말하기 실력을 연습해요. 비디오에서 사용된 자연스러운 표현과 논리적인 구조를 따라가면서, 전문 용어도 익히고, shadow speak 기술을 연습할 수 있어요. 특히 복잡한 개념을 쉽게 설명하는 방식을 분석하며, 영어 발음 교정에도 집중해 보세요!
핵심 어휘 및 표현
- Exhaustive testing: 철저한 테스팅 (예: "Exhaustive testing is not possible"은 "철저한 테스팅은 불가능하다"는 뜻이에요)
- Defect clustering: 결함 집중 (작은 수의 모듈에 대부분의 결함이 집중되는 현상)
- Pesticide Paradox: 살충제 패러독스 (반복된 테스트로 새로운 결함을 찾지 못하는 현상)
- Absence of error: 오류 부재 (결함이 없지만 사용자 요구를 충족하지 못하는 상황)
- Context dependent: 맥락 의존적 (테스트 방식이 애플리케이션의 종류에 따라 달라짐)
연습 팁: Shadowing을 잘하는 방법
이 비디오는 설명적인 내용이 많아 속도가 다소 빠를 수 있어요. shadowspeak 연습을 할 때는 먼저 전체 영상을 2-3번 듣고, 문장의 흐름을 파악한 후에 따라해 보세요. 특히 "Hence one of the testing principles states that..."와 같은 긴 문장은 구절로 나눠서 연습하면 발음 교정에 도움이 돼요. 목소리의 높낮이와 강세도 주의해서 따라해 보면, 자연스러운 영어 발음을 익힐 수 있답니다. 매일 10-15분씩坚持하면, 영어 듣기와 말하기 실력이 크게 향상될 거예요! 당신이 할 수 있어요, 파이팅!
쉐도잉이란? 영어 실력을 빠르게 키우는 과학적 방법
쉐도잉(Shadowing)은 원래 전문 통역사 훈련을 위해 개발된 언어 학습 기법으로, 다언어 학자인 Dr. Alexander Arguelles에 의해 대중화된 방법입니다. 핵심 원리는 간단하지만 매우 강력합니다: 원어민의 영어를 들으면서 1~2초의 짧은 지연으로 즉시 소리 내어 따라 말하는 것——마치 '그림자(shadow)'처럼 화자를 따라가는 것입니다. 문법 공부나 수동적인 청취와 달리, 쉐도잉은 뇌와 입 근육이 동시에 실시간으로 영어를 처리하고 재현하도록 훈련합니다. 연구에 따르면 이 방법은 발음 정확도, 억양, 리듬, 연음, 청취력, 말하기 유창성을 크게 향상시킵니다. IELTS 스피킹 준비와 자연스러운 영어 소통을 원하는 분들에게 특히 효과적입니다.