Shadowing Practice: Software Testing Mock Interview For Fresher Students | Manual Testing | Software Testing Interview - Learn English Speaking with Video
Creando lección...
1
Hi guys, welcome to the channel.
2
So as a part of this video, I'm going to take a mock interview for the skill manual testing with one of my subscriber.
3
Her name is Nikita.
4
She's a fresher.
5
So let's welcome her.
6
Hi Nikita, how are you?
7
I'm fine, sir.
8
Okay.
9
How are you?
10
Yeah, I'm good.
11
I'm good, Nikita.
12
So you're a fresher, is it?
13
What's up?
14
You're a fresher?
15
Yes, Yes sir.
16
Yes.
17
Okay.
18
Can you tell me something about yourself?
19
Yes sir.
20
Good afternoon sir.
21
Myself Nikita Mani.
22
Nikita.
23
Going forward call me Manish.
24
Okay sir.
25
Myself Nikita Mani.
26
I completed my engineering from Srimati Kashivayan Amalek College of Engineering Pune.
27
I love to work so that I can utilize my education in right way.
28
um coming to my technical skills i had done software testing
29
course sql uh my short-term goal is to get placed in a reputated company
30
and long-term goal is uh to become a respectable position in
31
that organizations that's it okay that's good uh from
32
which branch you have done your engineering uh mechanical sir okay
33
okay okay uh is there a particular reason why you are shifting from mechanical to testing field just wanted to ask
34
uh yes sir uh actually sir um
35
when my uh engineering is completed my engineering completed in 2019
36
uh from 2019 there is a very recession in the mechanical field
37
and also my interest is changes to the uh software
38
because in my company in my colleges there is a not
39
single company uh come to the college for the campus placements
40
and my interest also changed to the it industry okay
41
so i decided to switch the it it industry
42
and that's why i had done the software testing course okay
43
so you think one day you will achieve success in your software testing field
44
yes sir okay okay that's good to hear uh shall we start yes sir are you nervous
45
yes sir okay little
46
but sir okay nikita call me manish okay i just wanted to tell you
47
that don't be nervous even though you are not answering something
48
that's totally okay i'm there to help you maybe at the end of the meeting maybe through mail
49
or telegram anywhere but even though you're not answering something that's totally okay i'm very happy
50
that you came here to have an interview with me let me tell you
51
that many people out there don't have a courage to come here in front of me you have
52
that courage so be happy for that so let's start the interview yes
53
so can you tell me uh what is the purpose of doing the testing
54
uh yes sir uh actually testing is done uh for the for a for a specific reason
55
when the developer develop the software there is a person to
56
uh to test the application whether this application is defect free
57
or whether this application run according to the customer or requirement
58
or not for that reason we test the applications okay are you sure that when you are testing some
59
software you will give error free software to the customer are you sure about it just asking
60
actually sir it is impossible to send the software defect free but we are trying to to launch the software defect free.
61
Okay, that's interesting.
62
Okay, just tell me one thing.
63
Tomorrow you are testing something, maybe you are hired in some company, you are testing some application, you got some minor defects.
64
Yes sir.
65
You got some minor defect and will you still release the software?
66
Actually sir, this is authority to the test manager, this is not authority to the test engineer to launch the software uh
67
but if the uh if the
68
if the authority is uh is responsible to the me
69
but uh means test engineer uh i will not uh launch the software if the defect is present
70
okay okay okay nikita i just want to tell you
71
because you are a fresher out there
72
and many fresher people will be watching this video uh
73
when you are joining some company let's do not depend on my senior qa
74
or my qa lead you are the senior engineer you can take the responsibility of telling to the company
75
that we are not going to release the software to the customer
76
if it has you feel that that defect is
77
that defect can break something so it totally depends on the q engineer
78
if nikita is tomorrow joining some company it is nikita who need to say to his qa lead
79
or qa manager that i don't think that this software should go to the customer
80
and i feel that this minor issue needs to be fixed
81
and then it should be it should go to the production what i'm the reason i'm telling to you
82
because as a queue engineer you should never be silent you
83
should speak okay sir see queue engineer role is to like
84
you can you can do a lot of things you can
85
do a lot of things with your speaking skills you have to speak
86
when you have tested something you have got the issues you
87
have to raise it to the concerned people you have to
88
raise it to the qa lead you have to raise it to the qa manager you should not say
89
that okay whatever the decision you are taking i will be happy with
90
that no you should you know the application right
91
and you have found that found out that bug now it is nikita
92
or the fresher guy who has joined the company who need to take a decision whether he really feel
93
or she really feel whether this software should go into the production
94
or not you have to speak is what I'm trying to
95
say okay okay I am yeah yeah totally I totally agree
96
that if really it is a minor bug you can say
97
that okay even though we are going to the production there is no issue in
98
that but you have to explain you have to explain you have to explain the severity of
99
that bug to the your QA lead
100
or QA manager you you need to make them agree why you are saying
101
that this bug cannot go into the production getting
102
What I am trying to say here to all the freshers
103
out there who is watching this video is you need to speak.
104
You learn to speak not when you are becoming senior QA engineer or QA lead or QA manager, but as a fresher that will be very advantage for your career.
105
Okay Nikita, that's that's really impressive answer.
106
Let's move to the next question.
107
Just tell me tomorrow if you are going to some company
108
and you are the only software tester out there you are the first QA hired in the company
109
and there is no requirement they just give you the application to test it what will be your approach
110
which kind of testing you will be doing
111
okay sir uh in this situation uh i will do the exploratory testing uh
112
because there is a not requirement firstly i will understand the application how applications work
113
and then then i will test the applications in that situation i will uh do the exploratory testing okay okay sure
114
just tell me one thing
115
if i give you a login page of any application any bank application let's say
116
or any application any any application let's suppose uh i just tell you
117
that test this uh login feature what will be your first approach Okay, sir.
118
Sir, if there is a requirement,
119
then we check the requirement for the login page credential means in the login page there is a first name
120
or the last name.
121
That time we firstly check there is a means we firstly do the functional testing
122
that this login page accept this last first name accept the means capital letter
123
or the small letter or it accept the alphanumeric
124
or it accept only the numeric then we also derive the all possible scenarios and test this login page.
125
Okay.
126
Okay.
127
So you are telling that you will first understand the requirement.
128
That was I was looking for.
129
That's great answer.
130
Thank you.
131
So, you just tell me one thing, if you join some company, let's say it's a banking domain company,
132
it has a transaction field,
133
amount field which says that amount text field can accept amount between 50,000 to 1 lakh rupees in a particular one day.
134
What kind of scenarios that you can think of?
135
How you will break this particular feature?
136
Okay, sir.
137
That for the amount transfer, firstly we apply the text case design technique for 50,000 to 1 lakh.
138
Firstly, we check for the valid options that is between the 50,000 and 1 lakh we check for the 51,000,
139
50,000, 50,100, 60,000 and we also check for the invalid,
140
invalid numbers that is 49,000 or 20,000 and check whether it is properly,
141
means it is acceptable or not.
142
Okay.
143
So, you said you will apply here boundary value analysis.
144
Absolutely.
145
yes sir all design techniques test case equivalent partially also boundary value is also um
146
and the error guessing also
147
but uh boundary value analysis is the uh most uh most
148
important important is most uh proper proper test design technique uh
149
to the uh for uh more wide coverage of the test questions yeah i got it that's brilliant thank you
150
so you're really a fresher is it
151
yes sir fresher hand okay you are answering really nice i i i'm sure
152
that you were one of the topper in your college
153
or school is it so i mean sir uh in mechanical engineer i was topper
154
but uh in soft in it industry and not means i'm facing interviews uh
155
but i i'm rejected hey no sure man nikita i will
156
tell you one really good story uh what do you think
157
today am i doing good in my life in my software testing field you think
158
so yes sir do you really agree with me i mean do you really think
159
that i'm doing good in my software testing career i mean you
160
or i i'm me me me what you think
161
that am i doing good in my life in my software testing field
162
uh um actually i i just watch your videos and
163
so from this experience i i thought
164
that you are doing a good in your life no obviously i'm doing good in my life
165
but uh what i wanted to tell you that when I started giving job as a fresher,
166
I was rejected in my first 10 interviews and I was selected in my 11th interview.
167
So that's totally okay.
168
I mean, even though you're not getting selected now, I'm sure that you will get selected.
169
I mean, there is no need to tell your heart to be hurt.
170
Just work hard.
171
I'm sure
172
that you will get selected no issue yes yes okay tell me one thing yeah yeah tell me one thing
173
when developer will say that defect is not reproducible he is not able to reproduce it
174
when he will say
175
that okay sir uh uh miss uh miss not not reproducing this tester is able to see this defect
176
but developer can't see this this is the defect present in
177
the uh software uh this this is due to the due to improper build uh due to uh platform mismatching
178
or due to improper defect report created by the test engineer uh
179
or when the uh there is a uh there is a condition
180
that uh like technology is not supported by the
181
that particular features means suppose there is a gmail gmail gmail application and
182
that time the some some of the uh some of the
183
i mean some uh users users use the application login page uh
184
so this technology login means developer developer's technology is not supported by this login features
185
that time also a developer said this is not reproducible or
186
if the defect is if the defect is under the uh minor
187
or the uh minor of the major category
188
that time also a developer saying
189
that this is a not reproducible okay good answer thank you good answer can you give me two positive
190
and two negative scenario to test my whatsapp application
191
yes sir whatsapp means firstly positive application positive scenario is that
192
uh you know whatsapp application uh there is a video video option also we check
193
that don't tell me a story
194
but just tell me how you will write your test scenario
195
i want to know how you are framing the test scenario
196
is what i'm looking for that's all okay sir uh okay sir um to test the search number,
197
it's display or not.
198
It is a positive scenario.
199
And the negative scenario means whatever the search contact you means, whatever the contact detail you have saved, you are checking in what, sir? Is it?
200
Yes, yes, yes, yes.
201
Got it, got it.
202
Tell me.
203
Or negative is that when we, So, suppose in my contact list,
204
suppose there is one contact, it says the, suppose Shahrukh Khan,
205
and in WhatsApp, I search Shahrukh Khan and it is displayed on the WhatsApp application.
206
This is a negative scenario.
207
Okay.
208
Tell me one more negative scenario.
209
Suppose we in the WhatsApp,
210
we call the video call with a particular contact number and this video call goes to the another contact number.
211
Okay.
212
But we call the some particular person and the call goes to the wrong person.
213
Okay.
214
That's possible.
215
But okay, whatever you are telling is absolutely correct.
216
But I will tell you one negative scenario that you can test it is.
217
Let's say that in a WhatsApp feature, in a video call, let's say that maximum people that are allowed to do video call together, let's say it is eight number.
218
I don't know the exact number, how many people can do a video call together.
219
Yes, sir.
220
Do you know the number?
221
Yes.
222
No, actually I don't know.
223
But this is also negative.
224
I am not sure about.
225
So let's say in WhatsApp there is a limit that only eight people can do a video call together.
226
And now the scenario is you are adding the ninth person.
227
That's a good answer.
228
Thank you.
229
Can you tell me what do you mean by end-to-end testing?
230
Yes, sir.
231
End-to-end testing isn't nothing but the system testing.
232
In end-to-end testing, we test all the steps means uh suppose uh let's consider
233
uh amazon application uh in amazon application uh we are logging
234
with the uh our current credential um we uh we put the credential login and that time we uh
235
we search the product i do card product then buy the product
236
and uh payment the product this all testing uh means this means we test all the features of
237
that application this is nothing
238
but the end-to-end testing okay yeah got it uh okay give
239
me any integration uh test scenario in in any application let's
240
say okay sir uh okay sir uh i will uh means
241
that in gmail application uh suppose uh we uh suppose there
242
is compose application what's up okay sir uh we uh in whatsapp uh we uh means we write the message
243
and send it to a particular person uh suppose a a write the message
244
and want to send the message to the b b b person
245
and send the message to the b person
246
that then b was a uh p was on the was online on the whatsapp
247
and he also said the message sent by the a this
248
is also integration testing okay yeah that's impressive you know tell
249
me what do you mean by formal testing heard about this
250
term before yes sir nikita how come you know everything yes sir
251
because uh in lockdown i i'm i'm trying very hard yeah
252
that's good man that's really good frankly speaking i took many
253
rounds uh in this uh i mean from the time i i said
254
that i will be taking rounds many people came for the interview i took many freshers
255
but i even many rounds for freshers where they were they started shivering
256
and i had to stop the camera and i i had to set them
257
that okay take care
258
but you are really impressive that's really nice to hear that's why i got to know
259
that you you are a topper in your college
260
or school right that's impressive yes sir continue formal testing thanks
261
uh formal testing is a type of the smoke testing uh
262
in formal testing i mean suppose uh suppose test engineer write
263
the 20 test cases out of these 20 classes uh 15 test cases are passed
264
and five test cases are not passed means they are failed
265
that time test engineer said to all technical team that this application is not accepted.
266
Means test engineer rejected this software.
267
And this after that developer fixed that defect and said to the test engineer,
268
now test engineer refer all these 20 test cases and test the applications and test the application.
269
And this test engineer documents all the test cases.
270
uh means this is in the formal testing uh test engineer should uh should documents all the test cases
271
or documentation is a very uh very important thing in the
272
formal testing formal smoke testings okay okay i got it what you said
273
but i just asked about formal testing i didn't ask about
274
formal smoke testing i just asked about what is what is formal testing any idea miss uh informal testing
275
what sir sir actually my connection was loose
276
what i'm asking is uh like i didn't ask you about uh formal smoke testing
277
but i asked you about formal testing have you heard about this term formal testing
278
um actually sir i am i heard about the formal testing
279
is a type of the smoke testing formal testing is a
280
type of smoke testing okay okay i will tell you what is formal testing testing is nothing
281
but see there are two kind of companies
282
one company where you're able to hear me right yes sir
283
yes yes there will be two companies work company where they
284
will do not document anything they will not document your test
285
scenario they will not document your test they will not document
286
your bird tracking they will not document your traceability matrix they
287
will not track your defect tracking they will not track anything they will not track anything
288
that company is called yes
289
that kind of testing is called as informal testing informal yes sir i knew it
290
because i know that you know but i am just telling no issue
291
and then there comes the formal kind of testing where test
292
engineers they write tested scenarios they write test cases they write
293
traceability metrics they write bug tracking they send report they do everything they do everything in a very formal way
294
that is called called as formal testing getting me right yes
295
sir yes now just tell me in a formal company i
296
mean in a formal testing whether they will conduct post-mortem meeting or not
297
um yes sir okay yeah that's fine have you heard about the term called as usability testing Yes, sir.
298
In usability testing, we do not test the functionality of the application.
299
We only check the user friendliness of the application means how the application is user friendly.
300
Is application is, is application able to use the all the end users or not.
301
In user friendly function, in user friendly testing,
302
we only check the user friendliness of the applications can you give me some uh ideas by
303
which you will say
304
that this application is user friendly uh okay sir uh sir
305
um let us consider sir suppose there is a autocad application uh in actually autocad is not user friendly uh
306
because suppose we have to draw the some line uh
307
but in autocad application there is a there is option like a draw inside there is a line inside
308
that line there is a uh there is option also 2d
309
or 3d means we have to select the options uh inside
310
means of uh inside draw there is a line like inside the line there is a thick
311
or thin inside that there is a 2d
312
or 3d means there is a miss they this application have a two or two
313
or three more skills means this is the not the user
314
friendly applications uh user friendly application is uh uh suppose uh suppose there is a shadi.com uh website
315
and uh there is a so many uh
316
so many options like uh where use means uh who will miss uh looking for a broom
317
or bride or also there is so many options uh
318
so we suppose we select uh suppose we fill all the uh all the form
319
and uh click on the submit and
320
that then there is a no means there is no loading time means this is a user friendly applications
321
this loading time is not taking too much time.
322
Okay, okay, sure.
323
Okay, what I was looking here is you what I was expecting here is whatever you said is absolutely correct.
324
But what I was looking here is you do you know the meaning of placeholder?
325
Yes, sir.
326
Okay, what it is? yes sir uh placeholder means uh suppose uh there is a suppose a login login page
327
and there is a first name text field
328
and uh suppose we uh we move we put the our
329
cursor to the uh means text field of the first name
330
that time uh that time this application shows
331
that this is the first name okay got it got it yeah that's what i was telling
332
when you say your application is user friendly your application should teach the user how to use the application.
333
Do you agree with this?
334
Yes, sir.
335
Whatever you said is absolutely correct.
336
No issue.
337
I just gave you an idea.
338
Or to everyone who is watching this, we can tell even this option or even this answer.
339
No issue.
340
Absolutely great answer.
341
Yes, sir.
342
Can you tell me which model is called as iterative and incremental model?
343
Agile model, sir.
344
Tell me something about agile model.
345
Yes, in an Agile model,
346
both testing team and development team are working simultaneously so that when the project is assigned to a particular company,
347
that company spent this means launched this software to the customer in a very short span.
348
This is a big advantage of the Agile model.
349
In Agile model there are various roles like Scrum Master,
350
Product Owner or QA Team.
351
Just tell me one thing, tomorrow if you are joining the company, can you become Scrum Master or not?
352
No sir, I will become a Scrum team but not a Scrum Master.
353
you think a scrum master uh i mean what characters he should have that you are not having
354
yes sir a scrum master is a person who only noticed the what is the means
355
how is the process is going on whether the uh whether the team is working properly
356
or not whether the product is a whether the product is uh launched to the uh
357
to the customer is a as per the customer requirement
358
or the not scrum master is not the is a person
359
who is not responsible to the uh not responsible for the quality of the product
360
but is responsible to the all the uh all the activities uh
361
which is uh done during the um during the project
362
okay okay fine impressive but uh yeah fresher it is hard to become scrub master
363
But tomorrow if you are joining some new company let's say
364
or a startup company and you have almost off to two or three years of experience, that time they can make you strong.
365
And your job will be to take update from each and every one what they did today, what they are going to do today, what they did yesterday and is there any problem for them.
366
I mean instead of product manager or product owner involving in this stand up daily, they can make you scrum master
367
and you have to take an update from your type team members
368
and update to the uh maybe your engineering manager
369
or qa manager yes sir yeah fine uh have you heard
370
about the term called as release notes yes sir uh release note uh is a document
371
which contain uh
372
which is created by the test engineer uh it's contained uh
373
how many uh how many defects are how many defects present uh
374
which uh which defects are the uh fixed
375
which defects are going to be the uh fixed uh how
376
many test cases are passed how many test cases are not uh not passed
377
or how many total test cases are there i mean it
378
is a documents uh where uh where all the uh all the things are the uh noted and it is also
379
and in this document it also mentioned
380
that what is the uh what is the pressure what is
381
the procedures to install the software okay impressive great thanks nikita
382
uh my next question is can you tell me uh what
383
according to you should be the top qualities of any software testing
384
if you have read this question anywhere just erase it off
385
but i want to know from your point of view what
386
do you think the top quality should have any software tester should have
387
yes firstly firstly quality is to find the defects more
388
and more and the means test engineer should uh think beyond the uh beyond such a limit uh
389
so that the uh software is a software is a defect free
390
and the uh test engineer should be uh test engineer should be uh means
391
test engineer should be uh think uh more than
392
uh more than um means uh the common thing
393
and test engineer should have a quality for communication also.
394
Nikita can you tell me a few differences between retesting and regression testing?
395
Yes, sir.
396
Firstly, regression testing is testing the unchanged features,
397
testing the unchanged features to make sure that this unchanged feature is not impacted due to some changes like fixing the defect,
398
adding the features or many more changes to make sure that these
399
changes are not impacted to the unchanged features
400
and retesting means uh suppose a developer develop the software
401
and this software this software this software sent to the tester
402
now tester test the defect now tester test the application
403
and suppose he found the defect that time he he sent to the standard build
404
or application to the developer that time developer fix the defect
405
and again again send this application to the tester now this
406
tester through the testing this this testing is called as a retesting
407
means the testing the uh different testing the defect which is fixed
408
or not got it yeah yeah absolutely good answer thank you uh do you know what performance testing what it is
409
not a practical knowledge but just the theoretical knowledge do you have yes yes sir
410
uh performance testing means testing the risk of testing the uh testing the stability
411
and a response of a time by loading the uh by
412
applying the load uh it is called as a performance testing
413
um where stability means uh stability means uh uh ability to handle the number of the users
414
and the time response time is uh suppose we uh suppose
415
uh we uh in the suppose we in gmail application suppose
416
we enter the uh uh means we enter the username password
417
and click on the login
418
that time home page is the uh home page is displayed this is a response time
419
and load means how many uh how many users use the
420
application uh in a means at one time this this is nothing but the response time.
421
Sorry sir, performance testing.
422
Your answer is really awesome.
423
I mean just wanted to ask you like do you really watch my channel regularly?
424
Yes sir.
425
Okay, okay fine.
426
Have you heard about severity and priority?
427
Yes sir.
428
Tell me about it.
429
Severity means impact of the work
430
on the business workflow
431
and the priority means in priority means importance importance given to
432
the birds to fix it okay can you give me an example where severity and priority both are high
433
yes sir uh there are mainly there are four types of the severity uh critical uh blocker critical major
434
and minor uh example of the high severity
435
and priorities like uh suppose there is a um suppose there
436
is an uh application uh like we uh suppose we uh we go to the browser
437
and uh suppose there is a www.gmail.com and suppose there is a uh firstly there is a login page
438
and we enter the valid details means username and password
439
and suppose we uh we click on the login page
440
that time home page is not displayed means this is a high severity means uh this is a high severity
441
and priority is
442
that uh means uh suppose uh we enter the uh we we enter the website www.gmail.com
443
and that time uh login page is displayed and uh in uh in
444
that time uh suppose we enter the username password
445
and suppose there is a login uh login uh login page
446
have a spelling mistake this is also the high priority
447
because uh when we enter the gmail.com
448
and uh enter the valid details login is also means it
449
is the first page uh to display the all-in user this is also high priority yeah fix
450
that bug yeah sure okay have you heard about the term called as big bang method Big Bang.
451
Actually, I remember that this is the type of the integration testing exactly
452
but sir I'm not clear about that okay finally first question
453
that you are not sure of no no no I'm sure
454
that you know even this definition I will I will just
455
give you an example you will you will get to know have you heard about the
456
which is called as non incremental integration testing yes sir yes
457
tell me about it our non-incremented integration testing means in
458
that testing we don't about that we don't know about
459
that who is a parent and who is the children this is a non-incremented child module
460
yes yes okay who is a parent model
461
and who is the children okay tell me tell me is
462
it all tell me more about it uh i mean the definition of incremental integration testing how they will do the testing
463
uh in non-incremental uh non-incremental integration testing uh we uh we
464
actually uh know uh don't know about who is the parent model and who is the child model
465
no issue so see in non-incremental integration testing you do nothing
466
but since you are not aware of which is a parent module
467
and which is a child module you mix all the modules yes sir
468
and now you check the data flow between them now you check the integration testing between them
469
so this is called as non-incremental integration testing the other name
470
that is given to non-incremental integration testing is nothing
471
but big bank method okay sir it's just the other name of non-incremental integration testing
472
so you know even this one right yes sir uh can
473
you tell me how many principles are there in software testing have you heard about this um yes sir yes
474
uh it is mainly about seven to eight seven to eight okay it is exactly seven tell me any five
475
um first principle is
476
that uh firstly uh firstly uh to find the uh to
477
find the defect it is first principle uh second principle is
478
it is not impossible to uh to launch the software defect
479
free uh third where uh we should we should not do
480
the uh exhaustive testing uh exhausted testing fourth one is a cluster defect uh and the fifth one is a uh
481
uh fifth one pesticide pesticides yes i don't recall this pesticides paradox okay can you explain this what it is
482
uh means sir uh suppose there suppose there is an application
483
and which consider uh
484
which contains the four to five model uh let us consider four model a b c d
485
and uh in this uh suppose uh c and the developer fix that.
486
I'm not asking defect clustering.
487
Defect clustering.
488
Pesticides paradox.
489
Pesticides.
490
You were telling me that one, right?
491
What you were answering was defect clustering, right?
492
Defect clustering.
493
Yes.
494
Yes.
495
Yes.
496
actually I'm not recalling I know that
497
but I know I can't recall it see pesticides paradox is nothing
498
but if you are not update I will just start in case you are able to remember just start from there
499
yes you run the same set of test cases for a
500
longer run you will not be able to find out the
501
defects yes sir yes tell me tell me about it yes i i recall it uh suppose sir uh suppose
502
suppose consider one feature uh for this feature we create a test cases
503
and we uh we test this text cases means set up the test cases again
504
and again and that time our defect is limited so uh
505
so we have to we have to update our test cases
506
means means we have to add some more scenario to our test cases
507
so that our uh our test cases coverage is a wider
508
so that's it okay okay what you have said is almost correct
509
but so what i was telling is
510
if you have the same old test cases for a longer run
511
that means let's say my sprint is for 10 days
512
and after every 10 days i'm releasing the soft piece of
513
software to the customer now i have the set of test cases now
514
if i run the same test cases same set of test
515
cases every time i will not be able to find out the new new kind of defects
516
this concept is called as pesticides to come out of this
517
pesticides paradox we should keep on updating our test case document maybe after every two
518
or three days okay okay brilliant no issue can you tell me something about smoke
519
and sanity testing uh yes sir uh smoke testing means testing the testing the basic
520
and critical features at a high level to make sure
521
that application is working properly or not and the sanity testing is uh testing the basic and critical features
522
at one uh at one step uh at one step deeper
523
uh means uh means suppose there is a gmail account gmail account uh
524
and in gmail account uh there is a inbox inbox uh
525
in inbox suppose there is a mail uh in mail uh um in smoke testing we only checks
526
that in inbox this particular mail is present or not
527
and in sanity testing uh in sanity testing uh we test
528
that in the inbox there is a there is an one mail
529
and we test that this uh whether this mail is a uh whether this mail is forwarded
530
or not or we are able to uh we are able to reply to this mail particular mail
531
or not this is a sanity testing
532
and smoke testing is a wide and uh wide and shallow testing
533
and sanity testing is a narrow and deep testing
534
and smoke testing is a smoke testing is a positive testing
535
and sanitary testing is a combination of both positive
536
and negative testing smoke actually smoke testing is a automated
537
but sanitary testing is a not automated
538
and in smoke testing there is a need of the documentation
539
but in sanitary testing there is no need of the documentation
540
okay i will just tell you one scenario just tell me whether you will perform his smoke or sanitary testing
541
uh yes sir only scenario
542
or example sir i'm going to tell something you just tell me whether you will perform smoke
543
or sanity here okay sir okay okay tomorrow you're joining some company
544
and uh that software which you are working on which you will be working on it already had
545
1040 releases already it happened and now developer has given a new build to you you will do smoke or sanity first
546
sir can you repeat please okay tomorrow you are joining a company
547
and the software which you you are going to work on that software is already released 1040 times into the production
548
and now is giving you a new build
549
when you are receiving a new build whether you will perform smoke testing or sanity testing smoke testing sir okay okay
550
okay nikita i have uploaded a video which is like smoke
551
and sanity difference on my youtube channel i would request you to watch
552
that um no issue usually fresher will be not be totally understanding what is difference between smoke
553
and sanity i will tell you see until your build is
554
not at all stable right you are let's say tomorrow you are working in some new company
555
and until and unless your
556
basic and critical feature of the application is not stable you will perform smoke testing
557
once your system is stable once your software is stable every
558
time developer is giving you a new build you need to
559
perform sanity testing no need to worry i understand this
560
but i have uploaded a video on this topic it is
561
available on my channel just have a look it i have
562
mentioned nine points i'm sure you will understand it no issue
563
okay okay sir it was really nice uh talking with you uh
564
if i have to give any feedback from my side definitely i'm sure
565
that you're doing good in your life you have a good
566
knowledge of software testing really uh i'm sure like frankly speaking
567
what i was looking for you had all the capabilities you had all the answers
568
and all the answers were absolutely correct i'm really impressed uh i i'm sure
569
that in next uh maybe next one month maximum
570
i'm going to receive a mail from you saying
571
that uh hi sir or maybe hi manish the reason i'm telling hi sir
572
because and after telling you keep calling me manish you kept calling me sir okay
573
so i'm sure that after one month down the line i will receive a mail from nikita saying
574
that hi manish i got a placement in this company i'm sure you will get pleased
575
because you have a good knowledge
576
and i wish you all the success thank you i wish
577
you all the success yes sir i will tell me tell me
578
yes sir i will also try to uh place the company uh as soon as possible
579
because uh actually i miss um i i take on them
580
so many interviews uh two two three interviews uh in lockdown period
581
but there is a no reply from the company so i'm also confused that what is what is the
582
what is actually happened this time is not good as you
583
are you may be knowing already time is not good
584
because corona crisis time is not going good not only for freshers
585
but even experienced people are struggling a lot nowadays do not worry i i'm sure
586
that with time everything will change
587
and you will definitely get a job i mean i'm seeing
588
that spark in you and you will get it definitely yes sir
589
and also also sir i have a questions uh can you
590
ask please can you don't mind uh can you mail me
591
all the questions it is already one hour that's why i'm telling
592
yes sir yes i will reply to you no yes it
593
was really nice yes yes yes bye bye yes sir thank you
✨ Recomendar Video
B11
59 oraciones
HR Mock Interview| Top HR Interview Questions Asked | Fresher HR Interview Questions and Answers
Business EnglishInterview EnglishUniversity Students
B11
87 oraciones
Master the 'Tell Me About Yourself' Question with Confidence"
Business EnglishInterview EnglishUniversity Students
B21
202 oraciones
SOFTWARE ENGINEER Interview Questions & TOP SCORING ANSWERS!
Business EnglishInterview EnglishUniversity Students
B269
14 oraciones
Job Interview English 🇬🇧 | Real Conversation Practice (B1–B2 Level)
Business EnglishInterview EnglishUniversity Students
B1151 oraciones
How to ACTUALLY ace your cabin crew interview!✈️✨
Business EnglishInterview EnglishUniversity Students
B11
82 oraciones
Customer Support Mock Interview | Customer Support Interview Questions | Customer Support
Business EnglishInterview EnglishUniversity Students
C11
154 oraciones
Manual Testing: QA Interview Preparation Questions and Answers
Business EnglishInterview EnglishUniversity Students
B11
173 oraciones
Learn English with Movies/The Intern. Improve Spoken English Now. Job interview English.
Business EnglishInterview EnglishUniversity Students
B11
243 oraciones
Day 58 of English Speaking Practice
Interview EnglishDaily ConversationUniversity Students
B14
119 oraciones
Odd job interviews. | 6 Minute English.
Business EnglishInterview EnglishUniversity Students
B24
218 oraciones
My Entire Job Search Process: Software Engineer Resume & Interviews
Business EnglishInterview EnglishUniversity Students
B112
52 oraciones
Interview Etiquette - Good Example
Business EnglishInterview EnglishHigh School Students
Vocabulario y notas de pronunciación para esta lección
Esta lección de conversación de nivel B1 se basa en el vídeo “Software Testing Mock Interview For Fresher Students”. Las palabras que más se repiten: testing, sir, test, application, suppose. Este vídeo tiene 593 frases y 6764 palabras para practicar shadowing. La parte hablada dura 45:33. El hablante mantiene un ritmo constante de unas 148 palabras por minuto, cómodo para el shadowing. El 82 % de las palabras está entre las 3.000 más comunes del inglés; conviene repasar el resto antes de empezar.
Vocabulario clave de este vídeo
Las 15 palabras más avanzadas del vídeo, con su pronunciación y significado:
| Palabra | Pronunciación | Significado |
|---|---|---|
| defect sustantivo | /ˈdiːfɛkt/ | falla, tacha |
| scenario sustantivo | /sɪˈnɛəɹioʊ/ | escenario, supuesto |
| developer sustantivo | /dɪˈvɛləpɚ/ | desarrollador |
| sanity sustantivo | /ˈsæn.əˌti/ | cordura |
| firstly adverbio | /ˈfɜɹstli/ | primeramente |
| integration sustantivo | /ˌɪn.tɪˈɡɹeɪ.ʃən/ | integración |
| pesticide sustantivo | /ˈpɛstɪsaɪd/ | pesticida, plaguicida |
| tester sustantivo | /ˈtɛstəɹ/ | téster, tester |
| severity sustantivo | /səˈvɛɹ.ə.ti/ | severidad |
| requirement sustantivo | /ɹɪˈkwaɪɹmənt/ | exigencia, requisito |
| agile adjetivo | /ˈæd͡ʒ.aɪl/ | ágil |
| inbox sustantivo | /ˈɪnbɑks/ | buzón de entrada |
| cluster sustantivo | /ˈklʌstɚ/ | aglomeración, agrupamiento |
| sanitary adjetivo | /ˈsænɪt(ə)ɹi/ | sanitario |
| paradox sustantivo | /ˈpæ.ɹəˌdɒks/ | paradoja |
Phrasal verbs que vas a escuchar
| Palabra | Significado |
|---|---|
| find out verbo | averiguar, anoticiarse |
| stand up verbo | levantarse, ponerse de pie |
Frases que vale la pena repetir
Frases cortas y completas del vídeo que puedes reutilizar en la conversación diaria:
- Can you tell me something about yourself?
- What kind of scenarios that you can think of?
- How you will break this particular feature?
- Do you know the number?
- Do you agree with this?
Gramática en este vídeo
Las estructuras que más usa el hablante, con las palabras exactas del vídeo:
| Estructura | En el vídeo |
|---|---|
| Present perfect have/has + participio pasado — una acción pasada que sigue importando ahora | have done · have tested · have found |
| Voz pasiva be + participio pasado — importa lo que ocurre, no quién lo hace | is completed · is done · are hired |
| Oraciones de relativo who / which + oración — información extra sobre una persona o cosa | guy who has · everyone who is · person who only |
| Consejo con “should” should + verbo — decir qué es buena idea | should go · should be · should never be |
Pronunciación a tener en cuenta
El hablante usa 64 contracciones y formas reducidas, como I'm, don't, you're. Dilas en su forma corta, tal como las oyes.
- Los sonidos de “th”: theoretical /ˌθi.əˈɹɛt.ɪ.kəl/, ninth /naɪnθ/
- Los sonidos de “sh” y “zh”: integration /ˌɪn.tɪˈɡɹeɪ.ʃən/, fresher /ˈfɹɛʃ.ɚ/, credential /kɹɪˈdɛnʃəl/, documentation /ˌdɑkjəmɛnˈteɪʃən/, regression /ɹiːˈɡɹɛʃ.ən/
- Palabras largas — cuida el acento: developer /dɪˈvɛləpɚ/, integration /ˌɪn.tɪˈɡɹeɪ.ʃən/, severity /səˈvɛɹ.ə.ti/, sanitary /ˈsænɪt(ə)ɹi/, documentation /ˌdɑkjəmɛnˈteɪʃən/
Sonidos difíciles para hispanohablantes:
- s + consonante al inicio — sin añadir una “e” delante: scrum /skɹʌm/, stability /stəˈbɪlɪti/, scrub /skɹʌb/, startup /ˈstɑɹtˌʌp/, sprint /spɹɪnt/
- /v/ — no es /b/: los dientes tocan el labio inferior: developer /dɪˈvɛləpɚ/, severity /səˈvɛɹ.ə.ti/, exhaustive /ɪɡˈzɔstɪv/, iterative /ˈɪt(ə)ɹətɪv/, shiver /ˈʃɪvɚ/
- /z/ — sonora, no /s/: usability /ˌjuːzəˈbɪlɪti/, compose /kəmˈpəʊz/, exhaustive /ɪɡˈzɔstɪv/, utilize /ˈjuː.tɪ.laɪz/, exhaust /ɪɡˈzɔst/
Cómo practicar con este vídeo
- Escucha el vídeo entero una vez sin hablar y anota las palabras que no conoces.
- Haz shadowing frase por frase a velocidad normal, repitiendo cada una hasta que tu ritmo coincida con el del hablante.
- Grábate y compara con el original, prestando atención a palabras como defect, scenario, developer.
¿Qué es la Técnica de Shadowing?
Shadowing es una técnica de aprendizaje de idiomas respaldada por la ciencia, desarrollada originalmente para la formación de intérpretes profesionales y popularizada por el políglota Dr. Alexander Arguelles. El método es simple pero poderoso: escuchas audio en inglés nativo y lo repites en voz alta de inmediato, como una sombra que sigue al hablante con solo 1-2 segundos de retraso. A diferencia de la escucha pasiva o los ejercicios de gramática, el shadowing obliga a tu cerebro y músculos de la boca a procesar y reproducir simultáneamente patrones de habla reales. Las investigaciones muestran que mejora significativamente la precisión de la pronunciación, la entonación, el ritmo, el habla conectada, la comprensión auditiva y la fluidez al hablar, convirtiéndola en una de las metodologías más efectivas para la preparación del IELTS Speaking y la comunicación en inglés en el mundo real.