Prática de Shadowing: QA Automation Engineer Technical Interview questions and answers - Aprenda a falar inglês com vídeo
Escolha um modo de prática
Cada modo abre uma sala de prática em tela cheia.
195 frases
Se as frases estiverem muito curtas ou longas, clique em Edit para ajustá-las.
1
UA Automation Engineer Technical Interview Questions.
2
That's what you guys have been asking about for a while in a previous YouTube video.
3
So what I'm going to do is I'm going to answer
4
10 the most popular technical UA Automation Engineer interview questions for you, so you will know how the person with a 12 years experience would get those done.
5
But I'm going to answer it only for those folks who will hit that big fat thumb up button below right now,
6
who will subscribe to our channel and also join our Instagram and Telegram communities.
7
Links to each you can find right here.
8
Now, let me quickly introduce myself and then we're gonna get started.
9
My name is Sergei Kromchenko.
10
I'm a Software QA Engineer Lead Manager and a Senior Engineer Manager of SDAP in the past, but these days I'm helping people like Q to become a QA Engineer from scratch
11
or to improve your existing skills as a founder and a main mentor of Cognify.
12
Now, let's get into it.
13
Question number one.
14
What are the best candidates for the test automation?
15
Or, which test cases would you automate first?
16
Well, you should always think about why are you automating things?
17
Number one, because you want to get rid of a huge amount of manual job, right?
18
You want to get rid of that chunk of the job.
19
And how do you do that?
20
You automate the most repetitive tests.
21
Those tests that you run on a daily basis, every single day or as often as possible.
22
And those are usually regression tests.
23
So very first candidate is regression suite.
24
Number two, you should always think about a business logic.
25
What is the most important for your business?
26
And number three, you guys should always think, what is the most challenging or difficult test to be automated?
27
So you could take it and automate it so you wouldn't have to do it manually over and over again.
28
Those would be the best candidates for a test automation.
29
Question number two, what is a page object and how do you implement it?
30
Well, first thing first, page object is a programming design pattern.
31
It speaks for itself.
32
Page object model.
33
So we grab a page from the user interface that looks like this and we put it in terms of code.
34
We pretty much translate it into code where we create all of the elements such as buttons,
35
links, text fields, etc. And we put those in a class or object.
36
And we create helper methods such as login, such as logout, such as register.
37
So instead of you manually clicking navigate to login page, you clicking on the username, typing in your username, clicking on a password,
38
typing in your password, you create one method or a function called login
39
and you simply copy paste it in multiple places where you need to use it.
40
So this is a page object model.
41
That's why it's called page object because we're creating a copy, an object that looks like the page but in terms of code
42
and we can later reuse it
43
and how do you implement it well i kind of partially already described it you take your page
44
that looks like this where all of the selectors
45
or locators are visible and you would convert it to something
46
that looks like this where it's pretty much a human readable language
47
and by the way if you guys are interested in learning automation
48
and in going through up to 84 rounds of interview preparation throughout three months
49
and a half test automation course i'm actually hosting one at CodeMify.
50
So, if you're interested, I'm going to leave a link right below this video.
51
Let's continue.
52
Question number three.
53
And this one will mostly be related to Selenium WebDriver versus Cypress and Playwright.
54
Because implicit and explicit weight is something
55
that is already automatically taken off in most cases for playwright
56
and a cypress but in the selenium
57
or selenium based frameworks you will still need to worry about it implicit
58
and explicit weights what are they implicit weight is a weight
59
for the particular amount of time where we say hey wait for this locator
60
or this selector for as long as that
61
so what it's going to do web driver is going to be waiting for
62
that element to appear on the page
63
and constantly checking for it as soon as it appears on a page you will not look for it anymore
64
so it's not a hard it's not a threat sleep in java
65
or pause in cypress it's implicit weight explicit weight on the other hand will wait for very similar thing
66
but you wait for that element to be either clickable or visible or at etc. for a different status of that element,
67
not simply for it to appear on a DOM.
68
How do you handle dynamic or constantly changing elements?
69
That's a good question.
70
Number one, you find a static one, you find a one that doesn't change.
71
And you can build the path, you can use the X path, but I would recommend you to simply build a path from the parent or grandparent into child, whatever is unique.
72
If, or I would say, it's not even if, it's in every single case where you have issues with selectors or elements.
73
You should talk to your development team so software developers would add actionable elements
74
or they would add static IDs for every single actionable item on the page.
75
And what do you mean by that?
76
Buttons, links, text fields, anything that you can click and will do something on a page is an actionable item.
77
So every one of them should have some static, some test ID or whatever you want to call it, whatever want to call the attribute should have unique and static
78
value or an attribute so you could use it in your test automation that's the first thing
79
that you should always do when you join a company
80
and you see that they do not have anything static
81
and everything is dynamic level two answer to this question is
82
you actually do the job you ask hey can i get access to the ui repo
83
so i could start adding hooks or attributes for my test automation And if you can do so, or if they can teach you to do so,
84
you're going to get a raise in the near future, trust me, if you decide to do so.
85
How do you organize your test cases to ensure good coverage and easy maintenance?
86
Well, you could use some of the design patterns.
87
For example, page object model.
88
It will keep your tests well organized, structured, and somewhat scalable different programming patterns that you can use for your code,
89
but this is one of the most popular ones in the world.
90
Still, as of now, there are quite a few new ones coming in the world of JS, TS and quickly spreading into different frameworks and languages,
91
but regardless, page object model is the most popular one.
92
So, you will keep all of the tasks in a feature-like base or in a module-based structure,
93
and you will keep your tests maintainable as you will keep all of the locators
94
and helper methods in the particular pages that are easy to understand for the new people that join your company.
95
And how do you keep a good track of what is automated, what's not?
96
Well, you should always think of the traceability matrix.
97
That's the place where you kinda can know what's already automated or not.
98
And also, there are quite a few reporters that can also show you which areas are automated and which are simply not.
99
And by the way, if you guys having doubts if you should join a QA bootcamp or not, I did start a QA introduction week.
100
It's a whole week of the internship in a role of QA where you will go through a bootcamp, do the job for a US-based startup and try it if you actually like it or not.
101
If you're interested, I'm going to leave a link right below this video.
102
Let's continue.
103
How do you integrate task automation into CICD pipeline?
104
Well, that's kind of an interesting question, because you could use Jenkins, GitHub Actions, GitLab CI, AWS CI, or whatever they call it, regardless.
105
The question sounds like, how do you integrate it into CI?
106
Which means, CI is already there.
107
Which means, most likely, the question is about, by the way, you guys should double-check it.
108
Are they talking about integrating test automation into devs pipeline, or creating your own pipeline for QA team needs?
109
If you're talking about QA team needs, as simple as GitHub Actions, for example, by the way, link to which you can find right here, where I'm actually setting it up from scratch.
110
So in GitHub Actions, you simply create a YAML file and you specify what runs, when it runs, after which triggers, and how many threads do you run.
111
As simple as that, you can see it on that video.
112
If we're talking about devs pipeline that already exists and you have to integrate it into their pipeline, That's a senior as that question in my opinion.
113
Well, because I did it as the senior as that.
114
Usually, QA automation engineers would not be as involved, but when you're stepping into this game, you're pretty much getting upgraded to a senior position.
115
In majority of cases, some companies will be mid-level, but anyways, if you want it to be integrated into devs pipeline, number one, you have to talk to devs, see who created it, who maintains it,
116
most likely they're gonna have to do that
117
or even devops team sometimes as i did it in the past you could also do it as an as
118
that automation engineer or senior as
119
that the way i was you would have to chit chat
120
with the with the dev team understand their workflow have a
121
meeting with them to understand how you can integrate it where
122
exactly it will fit where exactly reports will be showing
123
and who will be checking those reports are those reports going to be checked automatically to continue ci cd process
124
or is it going to be a manual step to check all of the test automation results
125
and only then click button to release your software to your environment
126
or staging or even fraud it depends on your company setup
127
but definitely you should talk to your developing team before start doing
128
that that's a somewhat challenging one for newbies how do you handle authentication
129
and session management in your test automation well the very basic
130
way to handle authentication is simply create a user in interface
131
login helper method right you add your login helper method to every single test
132
and you wait for half of your life
133
because now you're you all of your thousand tests taking i
134
don't know five thousand more seconds than before not very scalable not very efficient in my opinion
135
but it works for the beginners then you decide like you look into it
136
and you're like well it's not efficient i'm wasting
137
so much time can i improve it somehow you definitely can by utilizing apis you can simply shoot an API request, get a response, get a token,
138
and then open up the page and inject it into local storage.
139
And then your page will be loaded as you're already logged in.
140
That's kind of the better option, but there's also another better option.
141
In Playwright, there is something called browser context.
142
Different frameworks have it implemented differently.
143
I think Playwright does the best job in it, where you can handle browser context, which means you log in only once,
144
you get that token stored in a local storage, everything that you need is stored in a browser, and you pretty much copy the browser context from one page, you paste it in another page,
145
you refresh it, and everything is already loaded.
146
You don't have to even send a request and get a response.
147
Even though API is a very fast way and a very efficient way,
148
browser context is even a better way to handle your authentication and a session management.
149
The next two are going to be quite challenging for newbies.
150
This one sounds like flaky tests.
151
How do you deal with them?
152
How do you troubleshoot them?
153
And how do you debug them?
154
Walk me through step by step.
155
This is, I would say, mid to senior level question where I would ask a lot of questions first.
156
Number one, you have to analyze what is happening.
157
Why is the test flaky?
158
And where is it flaky?
159
In the CI or neural local?
160
Is it flaky in the headless mode or in the headed mode?
161
Is it flaky when you run all the tests, only single file, or only single test?
162
When you answer all of those questions, you will very likely understand, I would say in the 70% of the cases,
163
you will likely understand why are those tests flaky and why are they failing?
164
If you did not, you should always look to into user interface.
165
I had quite a lot of flaky tests in my life and I can give you some of the examples.
166
User interface.
167
Whenever you have a certain side of the screen or whenever you start using scroll method of WebDriver.io or WebDriver any frameworks,
168
you will show a scroller bar on the right side and that scroller bar might be covering one of the buttons.
169
It did happen to me like seven or eight years ago.
170
The other case is
171
when an extra parameter passed into form data before sending API requests is causing to create two objects instead of one.
172
That's kind of insane but check your code, make sure there is nothing extra.
173
So flaky tests will honestly depend on quite a lot of things.
174
And the last and the worst case in my life that I had in flaky tests,
175
I couldn't find out why are some users failing randomly to log in until I have actually wrote a loop
176
and ran it 100 times until I found out that every 20th,
177
30th, 50th time it fails but it's a flaky backend for the login.
178
So it took me a while to figure that out, but even the backend can be flaky.
179
So guys, before you start digging into your code and to find out why is your test flaky,
180
make sure it's not a user interface or actually backend that is flaky.
181
This girl got it and that helped her to get a job offer.
182
I did torture her for two weeks.
183
I told her you have to automate CRUD, which is POST, PUT, GET, and DELETE.
184
She did automate it.
185
She spent two freaking entire weeks.
186
And guess what happened afterwards?
187
Well, she went for an interview in Europe and she got exactly same challenge.
188
And she've sold it in only two hours because she did suffer for two weeks.
189
She did say she hates me, but then she said she loved me because that helped her to get her job offer and to get 40% raised.
190
Make sure to watch her story because she did share a lot of secrets how to get a job.
191
And how can you guys also get a job?
192
Now, I want to thank you for your time
193
and I want to ask you guys to tell me
194
which were the most interesting interview questions that you did receive throughout your career.
195
Thank you and I'll see you next time.
Baixar aplicativo
Tudo o que você precisa para falar fluentemente
Pronúncia com IANota em cada frase
Prática de IPADomine cada som
VocabulárioMonte seu banco de palavras
Jogo de vocabulárioAprenda brincando
📺 Mesmo canal
✨ Vídeo recomendado
C11
163 frases
QUALITY ENGINEER Interview Questions & Answers! (How to PASS a Quality Engineer Job Interview!)
Business EnglishInterview EnglishUniversity Students
C12
239 frases
Excellent 2 Years AWS DevOps Engineer Mock Interview with Questions and Answers | Cloud | Docker
Business EnglishInterview EnglishUniversity Students
C12
257 frases
A/B Testing in Data Science Interviews by a Google Data Scientist | DataInterview
Business EnglishInterview EnglishUniversity Students
C18
24 frases
Introducing Automations: always-on coding agents
Business EnglishUniversity StudentsWorking Adults
C14
200 frases
10 JavaScript Interview Questions You HAVE TO KNOW
Business EnglishInterview EnglishUniversity Students
C12
154 frases
Manual Testing: QA Interview Preparation Questions and Answers
Business EnglishInterview EnglishUniversity Students
C12
188 frases
IT System Administrator Interview Questions and Answers | How to Pass an IT System Admin Interview
Business EnglishInterview EnglishUniversity Students
C14
24 frases
Financial Analyst: Top 3 Interview Questions & Answers
Business EnglishInterview EnglishUniversity Students
C12
129 frases
How to Become a Great Software Developer — Best Advice from Top-Notch Engineers
Business EnglishInterview EnglishUniversity Students
![[2026] TOEFL iBT Speaking Take an Interview | Step-by-Step Strategies #0008](https://img.youtube.com/vi/Bo4ARkCDQLk/mqdefault.jpg)
C12
160 frases
[2026] TOEFL iBT Speaking Take an Interview | Step-by-Step Strategies #0008
TOEFL PrepBusiness EnglishInterview English
C17
198 frases
2025 DevOps, SRE, Cloud Engineer Interview Questions: Ace Your Interview with This Guide
Business EnglishInterview EnglishUniversity Students
Vocabulário e dicas de fala para esta lição
Esta aula de conversação de nível C1 usa o vídeo “QA Automation Engineer Technical Interview questions and answers”. As palavras que mais se repetem: test, page, automation, flaky. Este vídeo tem 195 frases e 2642 palavras para praticar shadowing. A fala dura 13:55. O falante fala rápido, cerca de 190 palavras por minuto, então espere sons ligados e reduzidos. 83% das palavras estão entre as 3.000 mais comuns do inglês; vale a pena estudar o restante antes de começar.
Vocabulário principal deste vídeo
As 15 palavras mais avançadas do vídeo, com pronúncia e significado:
| Palavra | Pronúncia | Significado |
|---|---|---|
| automation substantivo | /ˌɔ.təˈmeɪ.ʃən/ | automação, automatização |
| automate verbo | /ˈɔ.təˌmeɪt/ | automatizar |
| pipeline substantivo | /ˈpaɪpˌlaɪn/ | ducto, duto |
| static adjetivo | /ˈstæt.ɪk/ | estático |
| helper substantivo | /ˈhɛlpɚ/ | ajudante |
| implicit adjetivo | /ɪmˈplɪsɪt/ | implícito |
| playwright substantivo | /ˈpleɪˌɹaɪt/ | dramaturgo, dramaturga |
| authentication substantivo | /ɔːˌθɛntɪˈkeɪʃn̩/ | autenticação |
| cypress substantivo | /ˈsaɪ.pɹəs/ | cipreste |
| selector substantivo | /sɪˈlɛktə(ɹ)/ | selecionador |
| selenium substantivo | /sɪˈliːni.əm/ | selénio, selênio |
| attribute substantivo | /ˈæt.ɹɪˌbjut/ | atributo |
| explicit adjetivo | /ɪkˈsplɪs.ɪt/ | explícito |
| newbie substantivo | /ˈnjuːbi/ | novato, iniciante |
| regression substantivo | /ɹiːˈɡɹɛʃ.ən/ | regressão |
Phrasal verbs que você vai ouvir
| Palavra | Significado |
|---|---|
| find out verbo | descobrir |
Frases que vale a pena repetir
Frases curtas e completas do vídeo que você pode usar na conversa do dia a dia:
- What is the most important for your business?
- How do you handle dynamic or constantly changing elements?
- How do you deal with them?
- How do you troubleshoot them?
- Thank you and I'll see you next time.
Gramática neste vídeo
As estruturas que o falante mais usa, com as palavras exatas do vídeo:
| Estrutura | No vídeo |
|---|---|
| Voz passiva be + particípio passado — o foco está no que acontece, não em quem faz | be automated · is automated · are automated |
| Orações relativas who / which + oração — informação extra sobre uma pessoa ou coisa | context, which means · CRUD, which is |
Pronúncia para ficar de olho
O falante usa 33 contrações e formas reduzidas, como I'm, you're, we're. Diga-as na forma curta, do jeito que você ouve.
- Os sons de “th”: authentication /ɔːˌθɛntɪˈkeɪʃn̩/, thumb /ˈθʌm/
- Os sons de “sh” e “zh”: automation /ˌɔ.təˈmeɪ.ʃən/, actionable /ˈæk.ʃə.nə.bəl/, authentication /ɔːˌθɛntɪˈkeɪʃn̩/, regression /ɹiːˈɡɹɛʃ.ən/, troubleshoot /ˈtɹʌbl̩ˌʃuːt/
- Palavras longas — acerte a sílaba tônica: automation /ˌɔ.təˈmeɪ.ʃən/, actionable /ˈæk.ʃə.nə.bəl/, authentication /ɔːˌθɛntɪˈkeɪʃn̩/, selenium /sɪˈliːni.əm/, manually /ˈmænj(u)əliː/
Sons difíceis para falantes de português:
- Consoante final — sem acrescentar um “i” depois: automate /ˈɔ.təˌmeɪt/, integrate /ˈɪn.tɪ.ɡɹeɪt/, static /ˈstæt.ɪk/, implicit /ɪmˈplɪsɪt/, playwright /ˈpleɪˌɹaɪt/
- /l/ final — a língua toca o céu da boca, não vira “u”: actionable /ˈæk.ʃə.nə.bəl/, clickable /ˈklɪkəbəl/, readable /ˈɹiː.də.bəl/, neural /ˈnʊɹəl/, scroll /skɹoʊl/
- /h/ — um sopro suave, diferente do “r”: helper /ˈhɛlpɚ/, headless /ˈhɛdləs/
Como praticar com este vídeo
- Ouça o vídeo inteiro uma vez sem falar e anote as palavras que você não conhece.
- Comece na velocidade 0,75×, faça shadowing frase por frase e volte à velocidade normal quando ficar fácil.
- Grave a sua voz e compare com o original, prestando atenção a palavras como automation, automate, pipeline.
O que é a Técnica de Shadowing?
Shadowing é uma técnica de aprendizado de idiomas com base científica, originalmente desenvolvida para o treinamento de intérpretes profissionais. O método é simples, mas poderoso: você ouve áudio em inglês nativo e repete imediatamente em voz alta — como uma sombra seguindo o falante com 1-2 segundos de atraso. Pesquisas mostram melhora significativa na precisão da pronúncia, entonação, ritmo, sons conectados, compreensão auditiva e fluência na fala.