background top icon
background center wave icon
background filled rhombus icon
background two lines icon
background stroke rhombus icon

Download "Собеседование на тестировщика ПО (Junior QA) №4"

input logo icon
"videoThumbnail Собеседование на тестировщика ПО (Junior QA) №4
Table of contents
|

Table of contents

0:00
Стартуем
0:08
Приветствие
0:52
Начало собеседования Алёны
1:04
«Расскажи о себе»
2:05
«Что такое тестирование»
2:49
«Что делать если нет требований»
3:36
Откуда еще взять требования?
4:53
Какие цели тестирования?
7:39
Какие виды и классификация тестирования
8:38
Расскажи про уровни тестирования
9:20
на каких уровнях тестирования ты будешь взаимодействовать как ручной тестировщик?
9:50
Расскажи про White/Black/Grey Box-тестирование
11:20
Расскажи про нефункциональные виды тестирования
14:26
smoke, sanity и regression когда проводятся и в чем отличия?
19:54
Зачем мы разделяем уровни тестирования с практической точки зрения (smoke, sanity и regression)
24:06
Разница между негативным и позитивным тестированием?
26:14
Правильный ответ на вопрос про позитивное и негативное тестирование
27:01
Для чего нужно деление на позитивное и негативное тестирование
29:24
Какие ты знаешь техники тест-дизайна
29:39
Что такое эквивалентное разделение, приведи пример
31:55
Зачем нам нужны классы эквивалентности
34:23
правильный ответ на «Зачем нам нужны классы эквивалентности?»
34:55
Граничные значения и зачем они нужны?
37:19
Доводилось писать тест-план? ЧТО ЭТО И ДЛЯ ЧЕГО НУЖЕН?
38:52
Что такое тест-кейс и чек-лист и для чего они нужны?
39:19
Расскажи про атрибуты чек-листа?
40:30
В каких случаях мы пишем тест- кейсы, а в каких чек-листы?
43:23
Что такое баг-репорт?
49:36
Какие бывают случаи в жизненном цикле баг-репорта?
51:42
Особенности тестирования веб приложений?
56:35
Расскажи про методологию разработки ПО?
59:48
Какие подходы к разработки ПО мы применяем в проекте?
1:01:07
Слышала про методологию Kanban?
1:01:58
Фидбек после собеседования
1:07:03
«НУ КАК ВАМ?БЫЛО ИНТЕРЕСНО?»
Video tags
|

Video tags

Тестирование
Testing
QA
Собеседование
Junior
Junior QA
Manual
Курс
Interview
ПО
Джуниор
Начинающий
Школа теситрвоания
Курсы
Subtitles
|

Subtitles

subtitles menu arrow
  • ruRussian
Download
00:00:00
[music]
00:00:07
hello everyone, Nikolay Cherkasov, a
00:00:11
tester with many years of experience and the
00:00:13
founder of the Cherkasov school,
00:00:17
today we have another interview with a
00:00:19
novice tester with an interview with
00:00:23
Alena, she has some experience in
00:00:25
testing projects, but not very
00:00:28
much and would like to try her
00:00:30
hand at junior and
00:00:32
if Do you want to participate in such
00:00:36
an interview, fill out the form via the link
00:00:38
below in the description or write to me in a personal
00:00:41
message as Alena did, let’s
00:00:44
support her with a like and kind
00:00:46
comments under the video, so watch
00:00:49
the interview, so
00:00:51
today Alena is with us Alena,
00:00:55
please tell me about yourself if you have
00:00:57
any... then experience testing for whom do you
00:00:59
want to be sorted to what
00:01:01
level
00:01:04
I want with interviewers ok engineer
00:01:08
John, I’ve completed
00:01:11
testing courses, that is, I want to test my
00:01:13
knowledge of
00:01:14
experience, I have
00:01:16
little experience, I tried it inside, I worked
00:01:19
from the front of the washer, I started bug
00:01:23
reports and all this time, that is, since about
00:01:26
December, I’ve been trying for myself from
00:01:30
Nesterovo the websites of this light stores
00:01:33
here are the last ones with test assignments I
00:01:35
came across any site I tested lunch
00:01:39
store for
00:01:45
documentation I’m familiar with whether I wrote checklists
00:01:48
and test cases but accordingly when the
00:01:50
robots ports are super this is great this is
00:01:54
great mobile applications
00:01:56
had to be subsidized when no no
00:01:59
this didn’t reach
00:02:01
well okay then let’s start with the basic
00:02:06
questions
00:02:08
what is testing
00:02:11
testing is a process whose purpose
00:02:16
one of which is to
00:02:19
make sure that the software itself
00:02:21
works as it should
00:02:23
meet the customer’s expectations
00:02:29
the customer’s expectations how are they
00:02:31
expressed in the
00:02:33
form of
00:02:35
requirements, that is, he lays out what
00:02:39
he wants, they accept, I will describe these certain
00:02:41
requirements and the egg will no longer need to be
00:02:43
implemented,
00:02:45
what to do if there are no requirements,
00:02:49
but most likely you need to talk about
00:02:52
what exactly he wants and create on
00:02:56
what he already wants this person
00:02:58
who collects it all moaned cumin and
00:03:02
creates these requirements the
00:03:05
person who collects what is the name of the
00:03:10
manager manager well and
00:03:14
if it so happens that there is no access to
00:03:18
the customer but it happened so he may
00:03:20
answer when there is no questions on
00:03:22
yours maybe he won’t answer you already
00:03:25
need
00:03:27
to on the basis of something it compiles test
00:03:31
documentation something else can be done
00:03:33
where to get the requirements
00:03:38
if you think like that, that is,
00:03:42
envious people are probably what the company wants
00:03:47
logically I don’t know there to think if there is
00:03:50
some form of
00:03:52
something logically at least already some
00:03:56
do the main thing
00:03:58
logically the main one will think, well, you’re
00:04:00
right,
00:04:02
it’s called using some kind of
00:04:04
formal logic, yes, that is, there are things
00:04:07
that we know a priori and we don’t need
00:04:10
this to be clearly stated in the
00:04:12
requirements because let’s say if we
00:04:14
test an online store, we roughly
00:04:16
suspect that in all
00:04:17
online stores have a shopping cart, that there is a
00:04:20
payment function, there
00:04:22
may just be some nuances we
00:04:24
may not know, but nevertheless, that is,
00:04:27
we can take the requirement from similar
00:04:29
services, we can invent requirements out of our heads
00:04:32
that correspond to the
00:04:34
general accepted approach, for example, to an
00:04:36
online store good good
00:04:41
you say that one of the goals
00:04:44
of testing is to compare expected
00:04:47
behavior with actual behavior, and what other
00:04:50
testing goals do you know about the
00:04:52
purpose of testing, that is, even tell us
00:04:55
whether the product is ready for release at all,
00:04:58
that is, how ready it is,
00:05:01
well, of
00:05:03
course, I didn’t name the goals
00:05:08
most likely as a consequence of the fact that the
00:05:10
expected and actual results, that
00:05:12
is, to minimize bugs, that is, so that there
00:05:15
is as little as possible
00:05:17
preventive such a method, that is,
00:05:20
on the one hand, we can always find bugs and
00:05:22
report them, and on the other hand, we
00:05:24
can somehow, as you say preventively
00:05:27
do so that there are
00:05:29
fewer bugs and
00:05:30
what does this involve such as magic
00:05:33
when we are warm in advance
00:05:43
but
00:05:52
in fact, that is,
00:05:56
when you test a program you not
00:06:00
only spoil the bug, but
00:06:03
you can also
00:06:05
give feedback to the
00:06:08
development team and, for example, point out
00:06:12
that here in the system, specifically, some
00:06:14
part of this system may not be
00:06:18
very well developed, there will probably
00:06:20
be bugs in it, because it
00:06:22
seems to you that she is right, then this is exactly
00:06:27
how you can help development
00:06:31
in advance, pay attention to those places where there
00:06:34
may initially be bugs that is, there
00:06:42
may be feedback for the development team, and
00:06:46
there may also be feedback for the
00:06:49
team not in technical terms, but in
00:06:53
terms of what the customer initially wanted,
00:06:55
that is, in addition to specific requirements,
00:06:58
we can see what the customer, for example,
00:07:01
would like, well, he has the main
00:07:04
idea of ​​a product, let’s say during the
00:07:07
development process you see that for some
00:07:09
reason
00:07:13
parts of the functionality are developed first,
00:07:15
some are important and some are not important, and you
00:07:19
can also give feedback and
00:07:20
say so guys, we don’t seem to have any bugs,
00:07:22
everything is correct, but here’s our development
00:07:24
something- that’s not what he’s focusing on, but
00:07:27
the customer wanted something
00:07:29
else to be done first and this is also like
00:07:33
one of the attributes of testing is
00:07:36
okay
00:07:39
okay let’s talk about the
00:07:43
type of testing you know some
00:07:45
classifications of types
00:07:48
well and standard functional
00:07:51
functional manual automated
00:07:54
testing
00:07:55
that’s
00:08:00
not there this is from Michael Big, that is,
00:08:02
unit testing,
00:08:05
integration testing of
00:08:07
already systems, this is stern and testing during
00:08:10
acceptance testing itself,
00:08:13
well,
00:08:17
well, there are many different
00:08:20
classifications that we have here and
00:08:23
acceptance modules are integration, but
00:08:25
acceptance modular integration
00:08:28
system is, in principle, we usually
00:08:31
call in theory levels testing,
00:08:33
well, as a rule,
00:08:35
then tell us in more detail what these
00:08:37
levels are about with the
00:08:39
most blinkers, this is unicast and that is,
00:08:43
some specific
00:08:45
one module
00:08:46
is being tested, and nothing else is being
00:08:49
touched on integration, also like
00:08:52
the interaction of two or more modules with
00:08:53
each other, the system is already being tested from
00:08:56
all cavities of the
00:09:01
system tested on the E100 briefly
00:09:03
accepted, that is,
00:09:06
either you are the customer or potential from
00:09:09
those who will be users, they are already
00:09:11
testing how inconvenient it is for them like them, is everything
00:09:13
okay there, does it meet
00:09:15
the requirements
00:09:18
well, you're like a pea, it's in syrup when
00:09:22
I think that at what levels of testing
00:09:23
you will be the most
00:09:26
most likely to act either modular and
00:09:29
integration modules for the time being this
00:09:32
skill will affect
00:09:34
the module it will most likely be the
00:09:36
developers or both
00:09:40
the system
00:09:44
and acceptance ones sometimes it’s good
00:09:48
that you don’t know about the boxes of multi-colored
00:09:52
balls and the white
00:09:57
black box and then when we don’t go into the
00:10:02
system itself, of course we don’t go to such a thing,
00:10:04
I don’t know what code is written like a capa for this
00:10:07
building, that is, this is basically the
00:10:10
customer’s requirement of a
00:10:14
white box, as we already know, while
00:10:18
you are still writing everything, the code itself understands this
00:10:21
logic, and that is, we ourselves from the posters are
00:10:25
absolutely correct, everything is correct Have you
00:10:28
ever heard about a glass box,
00:10:32
it’s the same as a white box, it’s just that in
00:10:35
some books it’s called white, it’s the
00:10:38
same thing,
00:10:41
but if he asks, now you know that
00:10:44
glass is
00:10:47
good, there’s also a tricky gray box,
00:10:50
which is very difficult to explain to everyone.
00:10:52
I’ve heard about this.
00:10:54
it’s not a completely clear boundary, it seems
00:10:57
like you need to partially
00:11:00
know something about the code, how much of it you need to know is
00:11:02
not entirely
00:11:04
true, it’s not clear to anyone, so
00:11:07
you can read 10 articles and they will
00:11:09
always differ from each other,
00:11:11
okay,
00:11:14
some non-functional types
00:11:16
of testing are you can you name those that are
00:11:19
not directly related to
00:11:20
testing the main functions of the system
00:11:27
at home,
00:11:30
for example,
00:11:33
graphical user interface,
00:11:35
how does it look like it corresponds to the
00:11:38
layout,
00:11:40
browser testing, that is, we actually have
00:11:43
two pints of this application, we
00:11:45
open a holiday of browsers like google
00:11:47
chrome, for example,
00:11:49
mozilla
00:11:52
microsoft, if we look at what is
00:11:55
really everything opens for us, everything
00:11:57
works well on different platforms,
00:12:00
for
00:12:07
example,
00:12:10
installation, that is, but it will most likely
00:12:12
be closer to a mobile application,
00:12:14
that is, that it is really an application that is being
00:12:17
restored, that for us it
00:12:19
is updated, everything is fine and that we
00:12:21
can hit it,
00:12:27
localizations, that is, that we, for example,
00:12:32
write well, as if for Russia, and even
00:12:36
inside it seems to me that Russia itself
00:12:39
has different time zones, having found that
00:12:41
the time is displayed correctly,
00:12:46
the localization is not quite the correct
00:12:49
time zone, rather
00:12:54
in Russia we have adopted one format
00:12:57
for displaying the date because for Russia
00:12:58
you are a wall localization is unlikely to be suitable
00:13:00
unless you check the
00:13:03
language of our republics, there is
00:13:05
some kind of Tuvan or Permian dialect like
00:13:07
hryvnia, but more if we are talking about
00:13:11
time, then it is the format for displaying the date
00:13:14
and time, here we are, for example, in the USA,
00:13:19
which is customary we have a 12-hour
00:13:22
day and m and p m and
00:13:26
in Europe, let’s say, well, in particular in
00:13:29
continental Europe in Russia we have a
00:13:31
24-hour way of displaying time,
00:13:33
so accordingly, when switching
00:13:35
locales, the display format should
00:13:37
change the date format, we have accepted day
00:13:40
month year and in America accepted month day
00:13:45
year here and or even year day month this is
00:13:50
often used except for the format for
00:13:53
displaying the date and for example the language what
00:13:56
else can change what do you think
00:13:59
if for example the same
00:14:02
clothing store is at least a currency that is, there
00:14:06
were before each country and it is different this
00:14:10
dimensional grid
00:14:12
because it is also varied
00:14:17
probably good enough in principle
00:14:21
okay well have
00:14:24
you ever heard of such types of
00:14:27
testing as smaug appreciate and regression
00:14:33
heard
00:14:36
able testing that is, and
00:14:39
only superficially like testing a
00:14:41
functionality build without going
00:14:44
into depth that God is more or less
00:14:46
stable drive it's about the same
00:14:49
thing but it's already going deeper that
00:14:51
it really works
00:14:52
the functionality of us is correct that's what it would have
00:14:56
left me already
00:14:58
stable
00:15:00
regression testing
00:15:03
testing when we release a new
00:15:06
feature we look at everything else that
00:15:08
was written and it's tested We are
00:15:10
stable and haven’t gotten anywhere, that everything
00:15:13
works, everything is fine, it’s somehow interesting that
00:15:16
the rule of the word stability is through all three
00:15:18
types of testing, and in the end I still don’t
00:15:20
understand how they differ from each other
00:15:22
if they all check stability and
00:15:24
everything is fine with us and stable
00:15:27
if you look at the smog and the balls they
00:15:29
check one parable about
00:15:33
[music]
00:15:39
how they differ from each other then they
00:15:42
themselves check one feature and give a
00:15:43
stable smog this is a superficial
00:15:46
check salt this is a more
00:15:48
in-depth check of the program
00:15:51
there is no functionality but smog is well
00:16:01
yes
00:16:03
what is the difference I was able to evaluate and
00:16:09
that they can do it faster, then they write the case
00:16:15
here and check, well, literally,
00:16:18
like the surface, that everything works after
00:16:21
all, everyone, that is, the
00:16:23
application as a whole works well, and sanity is
00:16:27
probably about specific functionality,
00:16:30
that is, it was able to check in a broader way, we
00:16:33
check that the entire application works more or less
00:16:35
in principle; this is what we need to
00:16:37
conclude that we can, in principle,
00:16:39
start testing sanity;
00:16:42
this is checking specific functionality
00:16:45
in depth; this can be either a new
00:16:47
functionality that has just been
00:16:48
written or some kind of optional functionality based on a
00:16:51
certain criterion That’s exactly the
00:16:54
same, and when we conduct sanity, we do not
00:16:56
conclude that, in principle, everything is
00:16:58
fine, we conclude that the
00:16:59
specific functionality
00:17:02
works great and is ready to be
00:17:04
added
00:17:05
to the general program, a piece of the general
00:17:10
regression of
00:17:12
Oreshkin of the same thing, when
00:17:15
they add functionality again, we
00:17:17
see that everything else
00:17:21
also works correctly, and everything else
00:17:25
that the rest of the steel sent
00:17:27
the rest of the functionality,
00:17:30
well, we sort of checked
00:17:37
the nationalities, added a new one and see
00:17:40
that the new functionality did not affect the
00:17:42
operation of the old functionality,
00:17:47
which means we will burn out the old
00:17:49
functionality in the process, but
00:17:56
so that when adding new ones,
00:17:59
work the old one,
00:18:01
evaluate it, but then why
00:18:06
1 functionality is it from after mine, how does
00:18:10
it interact with the steel ones, as
00:18:12
soon as she does it myself and then on the roof
00:18:15
regression when we check the new
00:18:16
functionality of the side, we check it, so here
00:18:18
we are
00:18:24
[music]
00:18:30
but this you are a little mistaken in general,
00:18:34
regression is exactly when we
00:18:36
check old functionality
00:18:38
that does not belong to the new one and we
00:18:41
check that the old functionality
00:18:44
works after we added
00:18:46
the new one and before that we check the new one within the
00:18:49
framework of appreciate testing, that is, we
00:18:53
checked that everything was able to quickly
00:18:55
more or less completely holds, then
00:18:59
we check the latest functionality
00:19:01
and then we check everything else within the framework of regression,
00:19:05
why do we need water, in principle, such a
00:19:07
three-level approach, you know, a
00:19:11
separate one could connect immigration,
00:19:13
they would take everything from the cases, they would immediately shove
00:19:17
thousands there from the sketch to and go through
00:19:19
what's the difference with max inter sinner, well,
00:19:23
it's like step by step 5 first we
00:19:25
carry out smog then we ourselves often lipstick
00:19:27
regression why is everything step by step body
00:19:30
why and so but if we
00:19:35
write everything it seems to me we just might
00:19:37
miss some bugs and
00:19:40
errors
00:19:42
something might not work correctly and
00:19:44
then all this is in this back in the opposite
00:19:46
direction to dig where that she goes
00:19:48
after the salary there is an error in the reverse
00:19:51
side of the c-class card, well, look, we
00:19:54
have tass cases, they are already written, they are already
00:19:57
written, that is, we cannot
00:19:59
let anything go, we have from the case we
00:20:01
go through them one by one, let’s say we have
00:20:03
1000 thousand cases, I don’t know about this, 50 are silent
00:20:07
there, 200 at the summit and there 750 are regression, so
00:20:11
we have a bunch of skism and for some reason
00:20:14
we highlight the smog regression and for some reason
00:20:18
we go through them specifically one by one according to
00:20:20
some logic that's why we do this
00:20:22
if for example we end up
00:20:24
passing all the checks anyway we had thousands of
00:20:27
kitty-kiss we would call them a bunch of tess
00:20:29
cases on me here you sit down and walk one by
00:20:32
one why do we need these levels the ticket
00:20:35
is probably connected development and
00:20:39
that is, it is written well, as if
00:20:42
development is gradually going on, that is, some kind of
00:20:47
functional one was written,
00:20:50
then put it then while solaris tests it,
00:20:53
writes new nationalists, we are already checking and
00:20:59
have carried it out accordingly, so it goes from the smaller to the
00:21:02
larger,
00:21:04
it gives out checked everything is fine
00:21:07
Everything works stably for us, that is, we take
00:21:10
the next one, while we look at the next one,
00:21:13
they write a trace, well, according to the
00:21:15
next ones, and just get out of the way, we’ve
00:21:18
already
00:21:22
checked the second functionality, we’re
00:21:24
doing regression testing that the
00:21:27
functionality is set to everything is
00:21:28
fine, and so it’s like, well smell .
00:21:34
During the development process, you correctly
00:21:36
described the types of testing, they are indeed
00:21:39
used in turn every time
00:21:41
we come up with a new
00:21:43
functionality,
00:21:46
but the essence of why we still divide 3 you didn’t
00:21:49
name, look, the simple fact is that
00:21:52
we do
00:21:55
n’t always get a stable build in the
00:21:56
buildings let's add its
00:21:58
functionality, sometimes after adding
00:22:00
new functionality the program does
00:22:02
not open at all and our task as a
00:22:05
tester is assigned to us; we receive the
00:22:07
next build to
00:22:08
make sure that the build is generally
00:22:11
worthy or available for
00:22:16
large-scale testing and therefore we need to highlight
00:22:19
individual cases that will simply check at the top
00:22:22
that the program, in principle,
00:22:24
works because if it doesn’t work in principle,
00:22:26
there is no point in
00:22:28
carrying out or hernia and delving into what
00:22:30
complex cases of old ones and it doesn’t
00:22:33
work,
00:22:34
appreciate it, we need to check the latest
00:22:38
functionality, as a rule, why do we
00:22:40
check the fresh functionality
00:22:43
because I just added it and
00:22:46
statistically the maximum number
00:22:48
of bugs and, well, most likely there is something wrong with it
00:22:50
because I just added it and
00:22:52
we check it secondarily after
00:22:55
you say that the program
00:22:56
basically works and is
00:22:58
regression-based and we check it
00:23:00
last because there is
00:23:03
no chance of finding bugs in there are
00:23:08
much fewer regression tests because regression
00:23:11
tests are something that was once valued, but
00:23:15
in the previous development cycle, we
00:23:18
already checked it once and then we
00:23:19
just put it all in a suitcase and keep it all,
00:23:23
and that’s why
00:23:24
some companies sometimes
00:23:26
even refuse regression to
00:23:30
save money time or they say, but you
00:23:32
check the regression and only if there is time
00:23:34
left,
00:23:35
therefore, precisely in order to
00:23:37
prioritize our workload,
00:23:39
we come up with these levels and
00:23:42
keep everything in our heads where we are now on the
00:23:45
project, where our latest feature is now,
00:23:48
in order to understand how deep it is today
00:23:51
we have to test and this is very
00:23:54
important, this is the groove from the practical point
00:23:57
of view when you will work,
00:23:59
so we are discussing this in depth,
00:24:02
this is quite a practical
00:24:04
question,
00:24:05
okay, but there is also a division
00:24:09
from cases into positive and negative
00:24:12
checks, you know what the difference is,
00:24:16
positive checks is how we
00:24:18
expect, that is, we are not trying to break
00:24:21
the system, we, since the user must
00:24:25
behave, we
00:24:27
check, so let’s say, friends
00:24:31
behave, the system names are already in the negative, that
00:24:35
is, we are non-standard and begin to own
00:24:39
checks, so
00:24:41
ideally, of course, so that if we don’t
00:24:46
know, we write a
00:24:47
case like this so that
00:24:51
the program works
00:24:54
positively, as if not about further, let’s
00:25:01
say
00:25:03
water, a positive attitude is directed, that is,
00:25:07
how the system works under normal
00:25:10
conditions, that is, normal, as if there
00:25:12
will be all the values ​​​​within the permissible limits of
00:25:16
accepting fields there, for example, negatively,
00:25:20
this, on the contrary, is already what is supposed to be
00:25:23
shouldn’t work, we just don’t
00:25:27
check how the system shouldn’t work,
00:25:29
it’s interesting, what is our expected
00:25:31
behavior in negative scenarios then
00:25:34
that the computer explodes or smoke comes out
00:25:36
or Korea
00:25:38
if we look at a calculator
00:25:42
[music]
00:25:43
divide by zero we can’t have this be a
00:25:45
negative check, that is and the soul of water
00:25:48
with an error, if we have a division by zero,
00:25:50
respectively, this is already a defect,
00:25:52
then it knows that as if a negative check is
00:25:55
not dependent, as if a
00:25:57
positive result is expected, we have to
00:26:00
set our error, but
00:26:02
in fact this is another thing, but with
00:26:05
positive ones, that is, this means it
00:26:10
gives 4 and
00:26:12
here you correctly named the example and not in
00:26:16
theory it didn’t work out well to write the
00:26:18
correct answer would be that we
00:26:20
expect that the user who
00:26:22
uses the system will either do
00:26:26
what
00:26:27
the system implies or something that
00:26:30
contradicts the logic of the system the system
00:26:33
itself is always
00:26:35
adequate should react to this
00:26:37
only if the positive scenario
00:26:40
is some kind of new, well, what is the
00:26:43
positive scenario, there was a
00:26:45
purchase in an online store, something else, and
00:26:47
if the user behaves as the
00:26:49
system would not want everyone to lead there,
00:26:51
some kind of error the tooltip is shown as
00:26:54
it pops up or the system simply does not
00:26:56
react, anything can happen, why do
00:26:59
we need such a division, what do you think,
00:27:02
but it seems to me that it is necessary because first of
00:27:07
all it carries out positive
00:27:09
checks to make sure that at
00:27:10
least a functional
00:27:12
sedan is really working correctly, the system
00:27:15
reacts only
00:27:17
then negatively is carried out that is,
00:27:20
finding bugs if everything is good,
00:27:22
positive and nothing shows up,
00:27:25
you just proceed to the negative ones so that you can
00:27:28
already check to exclude the already negative
00:27:30
scenario, why, well, let's check the
00:27:33
negative one first and then check
00:27:34
the positive one, and what's the difference,
00:27:37
but this may probably even be related to that
00:27:39
that initially we don’t need to find
00:27:41
errors, we don’t need to break the system,
00:27:44
but at least make it worse, that it
00:27:47
meets the requirements, that’s why,
00:27:52
according to the requirements, this is
00:27:53
positive, basically positive
00:27:55
positive checks, that’s why
00:27:57
they are carried out first, well, something
00:28:00
like this, in fact, a negativity scenario
00:28:04
can be indicated in the requirements for
00:28:05
example, what
00:28:08
error should be shown in the case of a
00:28:10
negative one? In fact, the problem is
00:28:13
that there are an infinite number of negative scenarios;
00:28:15
you can come up with them, come up with them, come up with them, come
00:28:16
up with them, the
00:28:18
user has some kind of keyboard shortcut and
00:28:20
entered that he threw some kind of virus at the input, it’s
00:28:23
not something else and this is forever forever
00:28:25
forever and you will do this endlessly
00:28:27
and in the end, instead of
00:28:29
testing the program, you will endlessly
00:28:31
come up with a negative scenario, so
00:28:33
in the industry they usually write the most
00:28:36
frequent and most basic
00:28:39
negative scenarios, for example, the user entered
00:28:41
the wrong login or password, but this is a
00:28:44
classic yes that is, how can you not
00:28:46
provide for such a case and you will,
00:28:48
of course, check these scenarios after
00:28:50
you check the positive scenario,
00:28:53
but there will always be some point in
00:28:55
the project where you will stop
00:28:58
to come up with a negative scenario and then
00:29:00
move on in testing, that’s why so as
00:29:03
not to endlessly generate
00:29:05
negative scenarios because
00:29:09
no matter how many of them are generated, there is still
00:29:10
a user who will come up with something that you ultimately
00:29:12
won’t provide for and that’s why it’s not worth it,
00:29:16
super ok
00:29:20
techniques, then from the design you know any
00:29:25
equivalence classes,
00:29:30
state transition boundary values ​​are there and tested in pairs
00:29:32
for there
00:29:34
I didn’t use pairwise ones, okay, let’s start with the simplest ones,
00:29:38
here’s equivalent divisions
00:29:41
worth
00:29:42
equivalent divisions such classes
00:29:45
within which the system reacts
00:29:48
in the same way and to any value inside
00:29:51
this class, so an example of a class can come out, for
00:30:02
example, we have an input field
00:30:05
taxes accept a value,
00:30:09
for example, only Cyrillic and Latin
00:30:11
no other forces, that is,
00:30:14
according to how popular
00:30:16
it will be the first
00:30:18
Latin and Cyrillic
00:30:20
characters and another class it will be the rest
00:30:24
sleeping symptoms of numbers and so on until it is
00:30:28
decided except for the Latin
00:30:30
Cyrillic alphabet they do not accept anything from where will the
00:30:32
numbers come from
00:30:39
no this other class of Cyrillic alphabet in
00:30:42
Latin portraits you say you
00:30:44
say let's say from from polyvoda
00:30:46
which accepts only Cyrillic alphabet into
00:30:48
Latin alphabet and
00:30:50
then you say here is an example of how we will
00:30:53
work here we have an
00:30:54
equivalence class let's say Cyrillic alphabet well
00:30:56
everything is correct up to this point there
00:30:59
is another equivalence class then numbers and
00:31:02
letters
00:31:03
symbols
00:31:07
special characters there as the scooter doesn’t know.
00:31:15
you shouldn’t accept and anything that we
00:31:18
see from it, as if the system should Krishna
00:31:21
didn’t understand this is the valence class for
00:31:24
negative scenarios
00:31:28
good
00:31:36
good in fact the Cyrillic and
00:31:39
Latin alphabet they also cannot be the same
00:31:41
class to valency this is true these are
00:31:43
keyboard symbols but since there are two
00:31:45
different alphabets, this is not separate, they are
00:31:48
not 1 lat, it doesn’t matter correctly, a good
00:31:52
answer is fine,
00:31:54
why do we need such an approach,
00:31:57
why do we need to enter some set like a spikelet of valence, yes, let’s say there are
00:32:02
symbols for input, what’s the point of
00:32:06
minimizing the number of tests, since it
00:32:09
can’t be limited in time,
00:32:12
so checking each character seems to be there
00:32:17
without knowing if by length, that is, you are the
00:32:20
same every time, we will have very, very
00:32:22
many tests, thanks to this, how do
00:32:26
we do the selection inside this class, that
00:32:30
is, accordingly, if it reacts the
00:32:32
same system, that is, we
00:32:35
will have much fewer tests, and why will you
00:32:37
show me apples 130 you
00:32:39
say everything correctly, everything you say is correct,
00:32:40
but it is necessary and specifically what will
00:32:43
save time here, so we declare for ourselves
00:32:46
that we have input data,
00:32:48
let’s say alphabetic symbols and we
00:32:51
use the technique of valence
00:32:54
separation,
00:32:55
which in the end, like this, we have a
00:32:58
real input field, take into account the alphabet,
00:33:01
so mine is here, here is an example from cases,
00:33:04
to understand how they save us
00:33:07
time and quantity,
00:33:12
for example, in the input field we enter there
00:33:16
in Cyrillic words, let’s assume any, no matter
00:33:20
what, can’t be cleaned and on the side in
00:33:23
Cyrillic,
00:33:25
accordingly, our system should be
00:33:27
responsive, everyone logged in well,
00:33:30
the following there we take if we have an empty
00:33:34
value, that is, our system says
00:33:36
that it’s empty, I won’t drag you, but roughly
00:33:39
speaking, this is it and this is a negative test like
00:33:43
you plus 1 more out of 1
00:33:46
character and we don’t know we wrote there!
00:33:50
. , . . and again he systematically says, well, no, it doesn’t
00:33:55
matter, we can even write one sign
00:33:57
there, two or three, on any small article, he
00:34:00
won’t miss it, accordingly, as if our
00:34:04
tests are being reduced, the tests are much smaller
00:34:07
than we will be letter a letter p letter you
00:34:10
there and so on, letter na checks we
00:34:14
can do an infinite number of test
00:34:17
cases and so we just entered
00:34:22
here I understand what you are saying, just the
00:34:25
most important thing is to say that we don’t
00:34:28
need and from each class to valence we
00:34:30
check all input data, that is,
00:34:33
let’s say 5 characters, we don’t need
00:34:35
to check all the articles we need urgently
00:34:37
check one or more,
00:34:38
depending on how many
00:34:40
letters we have minimum for the input, we don’t need to
00:34:42
check all the letters of the alphabet, check a
00:34:45
couple yourself,
00:34:49
it’s good and
00:34:52
give ethanal about the analysis of the boundaries of the
00:34:55
value, let’s talk about what it is, why it is
00:34:57
needed about the
00:34:59
boundaries of the boundary values, it often happens
00:35:02
that on the border
00:35:03
errors appear therefore and there are such
00:35:07
as such a design technique and if we
00:35:10
take for example the same pain and here and
00:35:12
and
00:35:13
it accepts from spots for example up to 15
00:35:17
characters
00:35:18
inclusive so we must check with
00:35:21
us the system is like a bonus there for example
00:35:24
two characters of it if from five to ten
00:35:30
then these are four symbols of the same meaning
00:35:33
you say he was given a chance theory then
00:35:35
we dive in
00:35:37
how many checks we usually need
00:35:41
in accordance with Kovalenko’s technique and
00:35:43
analysis boundary value
00:35:45
interval
00:35:47
here we have four so name what
00:35:52
they are 4 for example
00:35:56
border minus 1 value and the upper
00:36:00
limit the purpose is
00:36:02
good excellent and now we can
00:36:07
give an example here we have an interval
00:36:09
there from five to ten what specific
00:36:12
checks will you use
00:36:14
checks for four characters by 5 characters
00:36:17
by 10 1 cm
00:36:20
this will be put on 411 this will be
00:36:24
negative clerk and if there is an interval from
00:36:27
1 to a million, how much will we have
00:36:33
one million
00:36:35
million one
00:36:39
if there are 101
00:36:44
correct correct then the strength of this
00:36:47
approach is that no matter how long
00:36:49
our check interval will always be the
00:36:51
same, here in fact there is a
00:36:53
philosophical question how many should there be
00:36:55
be at a minimum where it is written 4 somewhere it is
00:36:57
written 5 that is, let’s say I read something
00:37:00
else inside the interval, you need to take a
00:37:02
random value so that
00:37:04
everything works there,
00:37:06
but that’s good, true, super
00:37:10
okay, let’s talk about the
00:37:14
test in the documentation, that is, the plan
00:37:16
had to be once - something to write and
00:37:19
about
00:37:21
40,
00:37:25
I understand what I read that this is a
00:37:30
document where we have an entry point for
00:37:32
testing the project, the race is
00:37:35
registered in the environment in which it will be
00:37:37
run, perhaps there is a version beat as it
00:37:42
were, these are all the nuances,
00:37:45
you said correctly approximately about the
00:37:48
entry points - output these are the criteria for the beginning and
00:37:51
end of testing
00:37:53
about the environment correctly that we
00:37:55
are selecting my environment and what else are we? well, there
00:37:57
may not be a build version of the VTS plan yet,
00:38:00
but they removed the exact one on the transport world of
00:38:01
Sybil, for example, and we can still indicate something there
00:38:11
[laughter]
00:38:17
well, here we go 5 with your fingers
00:38:21
there is formally an
00:38:24
industry standard on how to write it out, but there is a theory,
00:38:26
there is a lot of things you can do and
00:38:29
testing can be specified, you can specify
00:38:33
to write down in
00:38:35
which place, let’s say sprint, how the
00:38:37
stubble driver will be used, that
00:38:39
is, there is a lot there, well then I recommend
00:38:42
reading it separately, then at the end then I’ll
00:38:45
tell you
00:38:46
what the criteria are. at the end of the
00:38:48
tester we are specific, okay
00:38:52
test case checklist what is it and
00:38:55
why are they needed what do I include
00:38:58
h cell is a set of checks that is, without
00:39:02
going into depth a
00:39:04
set of checks or a case is already more
00:39:08
expanded
00:39:09
such checks where we already have and we have the
00:39:13
reproduction steps and what the expected result
00:39:19
looks like checking in the checklist, here is the
00:39:22
check itself, what is in it and
00:39:24
[music]
00:39:26
poisoning, we like to tidy up, we
00:39:30
need it, we have a sketch, you say the
00:39:31
bag and expect the result, but there is probably
00:39:34
some other name there so you can
00:39:37
identify
00:39:40
what a checklist is this is a check, a list of
00:39:44
checks, checks, a check list,
00:39:46
respectively, each check,
00:39:49
each check contains
00:39:52
some different fields, or else to
00:39:56
go check it myself,
00:40:00
I’ll briefly and briefly as a check what I
00:40:03
check
00:40:04
personally, mine is without going into detail, that’s
00:40:12
usually one name in itself, yes, there’s some
00:40:14
kind of crap that works, this
00:40:17
registration is successful there, it’s
00:40:20
so short, without any complex ones, but
00:40:30
why do we, in principle,
00:40:35
need these candles and crosses for the same thing to describe testing scenarios, that
00:40:39
is, it’s like for the same thing
00:40:41
necessary but has different complexity of description,
00:40:44
depth, why do we need such a problem, why do
00:40:46
n’t we use one thing, most
00:40:49
likely you will also be connected with
00:40:53
me by the development itself, what is
00:40:57
related to the
00:41:00
project
00:41:02
is used there somewhere, you will need to
00:41:05
check everything thoroughly, then it will be
00:41:08
accordingly pier cases
00:41:10
are carried out if you work somewhere, but
00:41:14
as if one tester understands what
00:41:16
you will be doing there and it’s not a very
00:41:20
large project, then it seems to me that you can
00:41:23
get by with the checklist itself, it
00:41:32
depends on the size of the project, yes, let’s say
00:41:35
if
00:41:37
you one is acceptable and you don’t need
00:41:40
to describe any complex checks to anyone,
00:41:42
it’s like the most taxing course, then you can
00:41:44
make checklists and that’s right, if
00:41:49
you’re not alone in the project, there are several of you, then it’s better, that is,
00:41:53
to do with it, the project is
00:41:57
quite large and requires but
00:41:59
I can write for myself because it
00:42:02
will be clear to another person if he
00:42:05
takes the same Sanych sheet, he may not
00:42:07
understand what I wanted to say by this, no
00:42:10
I did the test for understanding
00:42:12
for team work, so let’s say it’s true that
00:42:15
the beads understood each other everything is correct
00:42:18
and also somehow you think what can
00:42:21
influence the choice besides the size of the project
00:42:25
and let’s say the complexity doesn’t
00:42:34
know doesn’t come was
00:42:38
the amount of time let’s say even
00:42:41
if the project is very complex but you
00:42:44
just don’t have time to write a test of
00:42:46
the documentation you need to test but for
00:42:48
yourself you somehow want to secure some then a
00:42:51
testing plan for someone in some kind of
00:42:53
suite so that at least you can make notes somewhere and
00:42:56
you yourself don’t get confused, something you’ve already
00:42:57
passed that you haven’t passed here, you
00:42:59
would have to use a checklist, willy-nilly,
00:43:01
because you’re faster than a scribbler, and if there’s a
00:43:04
lot of time if the project is so
00:43:06
sticky, it always gives, I can if it’s a
00:43:09
sprint and long you don’t have every 2
00:43:12
weeks you have a release every two months
00:43:14
there, as a rule, you can write in more detail on the board and with and
00:43:16
so on
00:43:19
good
00:43:21
norms super
00:43:23
[music]
00:43:24
bug report what is that all includes
00:43:29
bug reports on you includes these ideas, that
00:43:33
is, the name, what the name is, what where
00:43:36
and under what conditions happens so that
00:43:39
another person who will
00:43:40
fix it understands
00:43:43
someone the same beginning, so let’s say
00:43:46
a flash drive, it looks like put cases on this
00:43:48
that this environment
00:43:50
is written, maybe what - the preconditions
00:43:52
are the same steps of reproduction, but the
00:43:57
bug report differs from the test case itself
00:44:01
in that there is an actual result,
00:44:03
that is, what do these steps lead to,
00:44:06
that we see it, which does not suit us,
00:44:08
but accordingly, there is already this there
00:44:12
may not necessarily be a
00:44:14
video application, for example, a tavern is produced or a
00:44:18
screenshot of where this tank is also located,
00:44:21
and in itself, as if this is the seriousness
00:44:24
of this bug,
00:44:25
that it can be critical there, it
00:44:28
can be very tank, but then it’s insignificant, it’s
00:44:31
still very important, well, not critical, yes without
00:44:35
it maybe a bug report, well, also, but for the
00:44:37
moment who is working the author
00:44:41
because the author is usually a
00:44:43
tester we whom he will
00:44:44
return in case of anything and which there
00:44:46
will be questions
00:44:50
generated behavior should also be
00:44:52
mentioned yes I understand you said the
00:44:54
same Poles essay but still said
00:44:56
almost
00:45:03
everything else is normal in principle and
00:45:05
true indeed, and
00:45:08
regarding seriousness this is a dangerous word
00:45:11
because in theory there are gradually
00:45:14
the words priority and there is seriousness and
00:45:18
let’s say in fat this field is called
00:45:21
priorities of seriousness there is no but in
00:45:24
some microsoft system for
00:45:26
storing tickets there there is a
00:45:29
priority to seriousness, there is a whole philosophy of how
00:45:32
to divide these concepts
00:45:34
accordingly,
00:45:35
you say in sports there is seriousness
00:45:39
only we can
00:45:42
or tula prices or maybe obscurity
00:45:46
only
00:45:50
priority priority shows us how
00:45:52
urgently we need to fix this bug not in chapters,
00:45:55
it also exists, that is, how
00:45:58
important it is this come shoot this
00:46:02
always it seems to me there is this
00:46:04
seriousness as if this is already this
00:46:07
is completely different this is how
00:46:09
seriously it affects the functionality everything is
00:46:14
correct everything is correct you say that everything is so
00:46:16
simple but now yes there is in jiri in the system
00:46:20
that uses 90 in the center of cases
00:46:22
there is no separate field of severity therefore
00:46:24
when you build a priority, you immediately
00:46:27
take everything into account and how dangerous it is,
00:46:29
how much of a hindrance it is, but in fact, most
00:46:31
often, if the tank breaks the floor of the system,
00:46:34
then usually it has a high priority,
00:46:36
but usually it only happens in case
00:46:40
of before, but nevertheless, good, great,
00:46:45
so
00:46:47
let's talk about the
00:46:49
life cycle of a bug report and what
00:46:52
happens to a bug report am in an
00:46:56
average system after you have
00:46:58
started it there and
00:47:00
I have already discovered dacia enamel, I assign it and
00:47:05
send it to the developers so that he
00:47:09
fixes it, so let’s say it’s true that
00:47:13
he also reproduces the interior of his exe,
00:47:17
so he doesn’t send it back that is, I’m already
00:47:21
looking at all the affairs of the hour, the pearl
00:47:24
tank closes and the real one is like this,
00:47:30
but it’s not always ideal,
00:47:34
what can be and is not so, it happens that
00:47:40
maybe it’s not a bug, it’s like the
00:47:44
behavior of this feature,
00:47:52
I’m checking, it
00:47:55
happens that it it doesn’t reproduce
00:47:58
dogs, it reproduces for me and then I need to
00:48:02
look here or at the checkout soared, I
00:48:05
look to see if everything is really
00:48:08
correct, I did it, we also have it, then most
00:48:12
likely we need to look with the
00:48:16
developer here, the conditions are
00:48:18
the same, we have the same immersion if we have a version of the build
00:48:22
we are different accordingly and
00:48:24
cannot understand each other, it
00:48:28
seems to me that in the extreme case if
00:48:30
everything seems to be perfect, you
00:48:33
will probably need to come here and
00:48:36
ask for advice, everything is correct, we will
00:48:40
get to the lead correctly if there is no team lead,
00:48:42
we can also write here and say that there is
00:48:46
such a guy here and
00:48:48
he then a person and not a person
00:48:51
who is responsible for all the products will say
00:48:54
either to the developer, come on,
00:48:57
try to find the tank to fix it, or he
00:48:59
will tell you okay, the tank is not scary, you think that it is
00:49:03
not terrible, put it aside where
00:49:05
they will close it, but you, as a
00:49:08
testing professional, are not you’ll forget to make a
00:49:10
bunch softer in the comments there, they told me
00:49:11
whether to postpone its closure there, in
00:49:13
fact, he acted so let’s keep it
00:49:15
in mind,
00:49:16
well,
00:49:19
we
00:49:21
thought about when everything is good with us,
00:49:23
then when we have a bar, at first the
00:49:27
developer writes it doesn’t play
00:49:29
in this, they decided more notes tank like this is a feature
00:49:32
and what else happens what do you think
00:49:35
in Natsik’s life bug report and when a
00:49:38
duplicate is most likely
00:49:41
years old you
00:49:43
also need to check here it’s captivating to
00:49:46
which gods and don’t give a [ __ ], well, what if this is a
00:49:50
bug that initially how to indicate that a
00:49:51
duplicate is closed or open and
00:49:55
if it is closed, which means it re
00:49:58
-opens, as in the opening, it does
00:50:01
stand in front of you once again baking
00:50:05
is carried out,
00:50:07
if it is open, then
00:50:11
it is possible that the
00:50:14
whole is the original one that will come back here in the
00:50:19
first thing we find out is that there
00:50:21
really was a duplicate because
00:50:23
sometimes the developers believe in me
00:50:25
it seemed like you saw something similar,
00:50:28
please look through the eyes of 150 open bugs
00:50:31
and this is what you will find there, that is,
00:50:33
this option does not suit us based on the
00:50:34
quotes, we say let’s click
00:50:36
the link to the double so that we do
00:50:39
n’t deal with all this, but if there is a link,
00:50:42
you really check first Is it a
00:50:44
duplicate because it might also
00:50:45
seem like, well, let’s say there’s a tank in the
00:50:48
login field, you check the password field and
00:50:49
they have different validity, not page 1, they’re
00:50:52
nearby, but still, if you
00:50:55
agree that there really is a duplicate,
00:50:57
you, as you said correctly, look at
00:50:58
the status here this original bug
00:51:00
that was then if it is still open then yes
00:51:05
you eat yours with Lenkov, just
00:51:06
add information and close it if the
00:51:10
original bug is already closed as
00:51:12
it was fixed or something else you do
00:51:16
as is customary in your project or you
00:51:18
Perry open it original tank,
00:51:21
if possible, you
00:51:23
need to add the same information, or you
00:51:25
change the status of your duplicate to nil, just
00:51:28
throw a link to the old grandmother and
00:51:29
say, well, it already happened, so let's
00:51:32
fix it and it will be easier for the developers, here you
00:51:34
already need to see how the team is good,
00:51:37
super
00:51:38
okay,
00:51:41
let's talk then That’s what you
00:51:46
were talking about, that you tested in the application and
00:51:51
you have some experience in this. Can you
00:51:54
tell us in principle the features of working
00:51:56
in the application and
00:51:58
what we need to build on when we
00:52:00
choose different types of testing, yes, that
00:52:03
is, but what should we pay attention to
00:52:06
specifically? application, as opposed to
00:52:07
native or hybrid ones, when we
00:52:11
test
00:52:15
I have when I look at the application
00:52:18
web applications tested it will be
00:52:20
restored for me, I think
00:52:23
registration and authorization,
00:52:27
but it also started as if there is so I’ll say
00:52:31
that
00:52:33
I broke everything down for myself into modules, it’s
00:52:36
just understandable, but if we, in principle,
00:52:39
approach from how these taxes
00:52:41
work to a
00:52:43
website of some kind or something else, if it’s just
00:52:46
more like
00:52:48
the picture above, let’s take that we, in principle,
00:52:52
check basically accepted degrees in the
00:52:56
application except and here’s the functionality
00:52:58
itself, what is it performs the main
00:53:00
functions and what else can we check? We
00:53:03
look at what the work in the application depends on,
00:53:09
namely, testing
00:53:12
would be suitable for a quad application, would not be
00:53:15
suitable for a decent application,
00:53:24
understands that this is testing,
00:53:34
that another new application is important,
00:53:37
cross-browser is probably important,
00:53:41
no longer browse work here it is important further,
00:53:45
we also have such types of
00:53:47
testing as testing for
00:53:49
interruption on there Albin 2, which is on
00:53:53
low Internet, that is, we need to look at
00:53:56
how much the Internet speed has a strong influence
00:53:59
on the performance because the
00:54:03
Internet companies that are accessible to them are correct
00:54:06
that maybe because
00:54:09
you are up to a
00:54:11
remote tester, we don’t need to knock out
00:54:23
exactly the hydrogen from the operating system,
00:54:28
it can be for the application, it can be like
00:54:32
load testing, the volume of a given
00:54:35
user enters the system and starts
00:54:39
using
00:54:43
[music]
00:54:45
then we have many types of
00:54:48
performance testers, including volumetric
00:54:49
testing and everything is correct there, we
00:54:52
test the server separately and test
00:54:55
that we have Internet speed, let’s allow
00:54:58
applications to work for us if there is a bad one,
00:55:00
sow from there all these that it shows,
00:55:02
here the negative is connected
00:55:06
cross-browser, we check here, but at the
00:55:09
same time we take into account that it
00:55:11
should not depend on the hardware power does not depend
00:55:14
on the operating system, in fact, because it
00:55:16
depends on the browser, so
00:55:19
accordingly, such things should be
00:55:22
kept in mind, and they may ask
00:55:24
about other types, let’s say about
00:55:27
native ones, and you can also, according to the
00:55:30
same classification for yourself
00:55:34
answer what are the features of the development of
00:55:37
native types, attach what installation is already
00:55:40
necessary, what depends on the operating system
00:55:42
on the hardware,
00:55:44
but let’s say the browser course I need
00:55:48
that the browser in the native one does not work and
00:55:52
if
00:55:54
you want further, you can tell me what else is
00:55:57
for the native one,
00:56:03
but in general, I understand well, there are also hybrid ones
00:56:07
also special too, how does a hybrid
00:56:10
application work and
00:56:12
time okay okay
00:56:16
normal
00:56:19
okay
00:56:21
okay then let's talk about
00:56:26
what let's talk about
00:56:30
development methodology and about how you
00:56:32
feel about the project someone gets here
00:56:35
we have different methodologies there are
00:56:38
some methodologies there are not
00:56:50
everywhere but how once the waterfall
00:56:53
model starts and since it is there everywhere there are drawings
00:56:56
from top to bottom that each stage is
00:56:59
gradually completed first
00:57:01
second and so on and so on this is a
00:57:03
return to the previous stage of the form it is
00:57:07
impossible it can actually be somewhere there
00:57:10
but it is very difficult to do it this is there
00:57:14
at the end we get the finished product at the
00:57:19
end of all the stages, so we got
00:57:21
the heel, that’s how
00:57:25
cool we got the product and we
00:57:28
know the
00:57:30
requirements, food that we always have, I,
00:57:33
they developed the requirements with us, the analysis, the
00:57:35
analyst did all this and
00:57:38
we already have them according to them and developers
00:57:40
do when development is over
00:57:43
tester does from but we already all know
00:57:45
what we want
00:57:48
you say why did we end up there
00:57:50
some kind of ajay you thought if
00:57:53
buns started this is a more flexible
00:57:57
methodology
00:57:59
that is, of
00:58:01
course there is no such clear concept of what
00:58:05
we were given and all the requirements are no longer
00:58:07
will be added no, and for each
00:58:10
print a requirement can be added, but
00:58:12
we also want this, she also wants
00:58:14
this, and we launch this, as if
00:58:16
flexible, and we get the output, but with
00:58:20
one sprint, for example, one version
00:58:23
2, the sprint is over, we add conveniently
00:58:26
for 2 version so on, that is, it is already
00:58:29
more flexible and
00:58:31
there is no such clear concept as that
00:58:35
one block has ended and another clearly begins,
00:58:38
and as if the connection with the other is not
00:58:40
extinguished, but the sprint ended in some
00:58:45
kind of format
00:58:50
[music]
00:58:52
but in essence, these are the sprint and these are the same,
00:58:57
that is, leading some actions in a row,
00:59:01
which is accustomed to the fact that the program
00:59:04
increases and improves, just ladies are
00:59:07
more global
00:59:10
mother or we measure at a waterfall and at
00:59:13
the end of the waterfall we usually end up with a
00:59:15
huge piece of program code and when
00:59:18
we move with these prints
00:59:20
little by little We make an increase to the program,
00:59:23
well, in the end, the program also grows just
00:59:25
cycles, in short, you described it correctly, you
00:59:29
roasted the approach correctly, in particular, Scrum about
00:59:32
this sprint and
00:59:33
waterfall,
00:59:35
feedback is difficult to
00:59:38
better work out at each stage all
00:59:41
these things there, the documentation is better written by the
00:59:44
mouse, they take more time, everything else
00:59:46
all this is true, but why do we need both
00:59:49
then and in this case, which
00:59:52
version of the development approach do we
00:59:54
use?
00:59:55
I think it also depends on the project,
00:59:58
what kind of project we have, there is a project that
01:00:01
requires everything clearly on the shelves,
01:00:04
the model will fit very well,
01:00:08
but this most likely there may be
01:00:10
something connected there, the
01:00:13
river with the mystical, not programs
01:00:16
like medical ones, but if the same
01:00:21
store does not require such a clear one, and
01:00:24
every time we want something like this, it’s
01:00:29
clear that a flexible scran will be better suited here,
01:00:37
it will be here
01:00:39
rather than there you further through
01:00:43
we will issue
01:00:45
an update for a somewhat long time, well, yes, that is, it reacts faster to
01:00:49
changes in reviews, that’s why
01:00:52
waterfall is also important to us how
01:00:55
big the cost of an error is, because if the
01:00:57
online store is bad, it’s not
01:00:59
the same as if the rocket
01:01:03
is good,
01:01:04
right, but there is also water or besides from the crane I
01:01:08
also heard flounder when
01:01:12
I heard the name, yes, I still didn’t quite
01:01:15
understand the differences between them and
01:01:17
from the crane
01:01:21
with me there
01:01:23
are no sprints from the company, that is, we
01:01:25
are talking about planning any based on
01:01:28
each task separately and there are
01:01:30
no such
01:01:33
clear sprints which either something needs to
01:01:35
be done or thrown out of the blog and so
01:01:37
on, that is, prints and can be
01:01:39
moved away,
01:01:40
they are not so fixed and
01:01:44
this has its pros and cons, but it’s better for
01:01:47
you to read
01:01:49
then
01:01:51
okay okay, basically we
01:01:55
discussed a lot of things,
01:01:57
almost everything I wanted
01:02:00
what my feedback, look, I don’t recommend
01:02:04
learning any one definition
01:02:07
that this is testing because I
01:02:09
tried to formulate it on the fly, it did
01:02:11
n’t work out very well, just learn,
01:02:13
take which simple definition is the
01:02:15
simplest, that is, the source of the book from
01:02:18
2004 states that testing is a
01:02:22
compliance check
01:02:24
between the expected actual behavior of
01:02:26
the program, carried out on a
01:02:28
set of tests selected of course, a certain
01:02:31
everything and it
01:02:33
will be easier for you, you won’t have to
01:02:36
try to come up with something for yourself in stress there, for
01:02:42
testing purposes, too, somewhere there are
01:02:46
different classifications of testing purposes,
01:02:47
but we just started saying you she said
01:02:49
that one of the goals is to search for bugs and
01:02:51
then how difficult it became here, so
01:02:53
accordingly somewhere we’ll take
01:02:55
some kind of list of these goals so that
01:02:59
in addition to searching for blogs there is something to
01:03:01
provide feedback on the quality of the
01:03:03
product
01:03:05
[music] to the
01:03:13
element itself like me called it well, it
01:03:20
shouldn’t have been very clear, maybe you
01:03:22
know, I just recommend repeating,
01:03:24
let’s take a simple classification, simple
01:03:27
so that you don’t have to, so that you can understand it in 1
01:03:31
hour and all other types of
01:03:33
testing are basically normal
01:03:37
about the gray box, you can read
01:03:40
what you don’t and not everything interiors know
01:03:42
about the sire box, too, not everyone likes to talk about it
01:03:44
and discuss it, so
01:03:47
appreciate it, we’re silent, we’re sinning to repeat it, why do
01:03:51
we need it, I explained it, but anyway, so that I could
01:03:53
fasten it for myself, so it’s good, the level of
01:03:57
testing was good, the techniques were good,
01:04:00
well, norma, in principle, it’s just necessary
01:04:04
first of all them from a theoretical
01:04:06
point of view and then give an example
01:04:07
when you give an example it immediately
01:04:09
seems that now I’ll
01:04:11
explain with an example in the end
01:04:14
everyone has such a classic
01:04:17
well so the State Planning Committee has such a
01:04:22
source
01:04:26
829 quality standard a
01:04:29
and the letter a and and three letters and English
01:04:33
as in food products,
01:04:36
there is such 829, it was generally
01:04:41
created to describe how best
01:04:43
to test in industry,
01:04:46
but it is quite suitable as a source
01:04:49
for
01:04:51
developing software programs and there are
01:04:53
things that should be there in
01:04:56
terms of what
01:04:58
to test, what will be tested, how
01:05:01
people criteria beginning ending this is
01:05:04
all just written there here is a
01:05:07
checklist sketch good bug report also in
01:05:11
principle everything was fine
01:05:14
so it was discussed here the principles of the
01:05:18
applications are a very important question from a practical
01:05:21
point of view because when you
01:05:24
knock on the door for a specific interview
01:05:26
very now the program in the vacancy will be
01:05:29
indicated We develop hybrid
01:05:31
applications, or we have a native application,
01:05:33
or we have web applications, and when you
01:05:35
get an interview, you will already
01:05:38
roughly understand what they will
01:05:40
ask based on the fact that they have
01:05:41
something quickly style, so you will read
01:05:45
about the principles of work first queue in the
01:05:48
application of native or accessible and
01:05:50
hybrid and then, based on this,
01:05:53
think about what types of tester you
01:05:55
use for each type of application,
01:05:58
whatever music you use, in contrast,
01:06:01
create understands that
01:06:02
the approach can really be different, it will be
01:06:05
necessary to be different, and so on, and everything
01:06:11
else in principle normas, well, about
01:06:15
Kanban, read a miracle, what is really
01:06:16
different from Scrum because it is not
01:06:19
very different, they are combined with something,
01:06:23
let’s say a Kanban board is handed over to this chair and
01:06:25
eyebrows, it has already been transferred to Scrum and to
01:06:27
other places and there is confusion,
01:06:30
almost
01:06:33
everything is basically with me no more questions
01:06:36
you have some questions
01:06:39
let me work, what
01:06:41
[laughs]
01:06:46
good
01:06:48
then good luck to you in repeating the
01:06:52
bottlenecks and finding work before such a
01:06:56
big one
01:06:57
please let's go bye well,
01:07:02
how were you interested if so then like it,
01:07:07
start the fireplace and recommend
01:07:10
the video to those As a novice tester,
01:07:13
I want to thank Alena for participating in a
01:07:16
similar interview format and living for her
01:07:18
to get the desired job as quickly as possible. I
01:07:20
also remind you that if you want to
01:07:23
participate in such an interview,
01:07:26
fill out the form at the link below in
01:07:28
the description or write to me in a personal message before the
01:07:31
new video bye bye
01:07:35
[music]

Description:

Записывайтесь/подписывайтесь: Визитка https://beacons.ai/ncherkasov Форма для записи на публичное собеседование https://cherkasovschool.zenclass.ru/public/course/b039abbd-01cc-4c9d-8f91-83fc1fcb8879 Форма для записи на приватное собеседование https://cherkasovschool.zenclass.ru/public/course/5faf7907-506b-4dc9-9158-94a0080a1810 Бусти https://boosty.to/cherkasovschool (откроется доступ на закрытый канал + дискорд сервер с полезной инфой) Телеграм личка https://t.me/ncherkasov01 Школа в Телеграм https://t.me/cherkasovschool Школа в Вконтакте https://vk.com/cherkasovschool (в обсуждениях есть Отзывы) Если хочется послушать видосы в качалке/пробежке/за рулём помимо ютуба: Apple podcast: https://podcasts.apple.com/us/podcast/cherkasovschool/id1743985240 Yandex podcast: https://music.yandex.ru/album/22671918 Google podcast: https://podcasts.google.com/feed/aHR0cHM6Ly9wb2RzdGVyLmZtL3Jzcy54bWw_cGlkPTgxNTIz Таймкоды: 0:00 Стартуем 0:08 Приветствие 0:52 Начало собеседования Алёны 1:04 «Расскажи о себе» 2:05 «Что такое тестирование» 2:49 «Что делать если нет требований» 3:36 Откуда еще взять требования? 4:53 Какие цели тестирования? 7:39 Какие виды и классификация тестирования 8:38 Расскажи про уровни тестирования 9:20 на каких уровнях тестирования ты будешь взаимодействовать как ручной тестировщик? 9:50 Расскажи про White/Black/Grey Box-тестирование 11:20 Расскажи про нефункциональные виды тестирования 14:26 smoke, sanity и regression когда проводятся и в чем отличия? 19:54 Зачем мы разделяем уровни тестирования с практической точки зрения (smoke, sanity и regression) 24:06 Разница между негативным и позитивным тестированием? 26:14 Правильный ответ на вопрос про позитивное и негативное тестирование 27:01 Для чего нужно деление на позитивное и негативное тестирование 29:24 Какие ты знаешь техники тест-дизайна 29:39 Что такое эквивалентное разделение, приведи пример 31:55 Зачем нам нужны классы эквивалентности 34:23 правильный ответ на «Зачем нам нужны классы эквивалентности?» 34:55 Граничные значения и зачем они нужны? 37:19 Доводилось писать тест-план? ЧТО ЭТО И ДЛЯ ЧЕГО НУЖЕН? 38:52 Что такое тест-кейс и чек-лист и для чего они нужны? 39:19 Расскажи про атрибуты чек-листа? 40:30 В каких случаях мы пишем тест- кейсы, а в каких чек-листы? 43:23 Что такое баг-репорт? 49:36 Какие бывают случаи в жизненном цикле баг-репорта? 51:42 Особенности тестирования веб приложений? 56:35 Расскажи про методологию разработки ПО? 59:48 Какие подходы к разработки ПО мы применяем в проекте? 1:01:07 Слышала про методологию Kanban? 1:01:58 Фидбек после собеседования 1:07:03 «НУ КАК ВАМ?БЫЛО ИНТЕРЕСНО?»

Preparing download options

popular icon
Popular
hd icon
HD video
audio icon
Only sound
total icon
All
* — If the video is playing in a new tab, go to it, then right-click on the video and select "Save video as..."
** — Link intended for online playback in specialized players

Questions about downloading video

mobile menu iconHow can I download "Собеседование на тестировщика ПО (Junior QA) №4" video?mobile menu icon

  • http://unidownloader.com/ website is the best way to download a video or a separate audio track if you want to do without installing programs and extensions.

  • The UDL Helper extension is a convenient button that is seamlessly integrated into YouTube, Instagram and OK.ru sites for fast content download.

  • UDL Client program (for Windows) is the most powerful solution that supports more than 900 websites, social networks and video hosting sites, as well as any video quality that is available in the source.

  • UDL Lite is a really convenient way to access a website from your mobile device. With its help, you can easily download videos directly to your smartphone.

mobile menu iconWhich format of "Собеседование на тестировщика ПО (Junior QA) №4" video should I choose?mobile menu icon

  • The best quality formats are FullHD (1080p), 2K (1440p), 4K (2160p) and 8K (4320p). The higher the resolution of your screen, the higher the video quality should be. However, there are other factors to consider: download speed, amount of free space, and device performance during playback.

mobile menu iconWhy does my computer freeze when loading a "Собеседование на тестировщика ПО (Junior QA) №4" video?mobile menu icon

  • The browser/computer should not freeze completely! If this happens, please report it with a link to the video. Sometimes videos cannot be downloaded directly in a suitable format, so we have added the ability to convert the file to the desired format. In some cases, this process may actively use computer resources.

mobile menu iconHow can I download "Собеседование на тестировщика ПО (Junior QA) №4" video to my phone?mobile menu icon

  • You can download a video to your smartphone using the website or the PWA application UDL Lite. It is also possible to send a download link via QR code using the UDL Helper extension.

mobile menu iconHow can I download an audio track (music) to MP3 "Собеседование на тестировщика ПО (Junior QA) №4"?mobile menu icon

  • The most convenient way is to use the UDL Client program, which supports converting video to MP3 format. In some cases, MP3 can also be downloaded through the UDL Helper extension.

mobile menu iconHow can I save a frame from a video "Собеседование на тестировщика ПО (Junior QA) №4"?mobile menu icon

  • This feature is available in the UDL Helper extension. Make sure that "Show the video snapshot button" is checked in the settings. A camera icon should appear in the lower right corner of the player to the left of the "Settings" icon. When you click on it, the current frame from the video will be saved to your computer in JPEG format.

mobile menu iconWhat's the price of all this stuff?mobile menu icon

  • It costs nothing. Our services are absolutely free for all users. There are no PRO subscriptions, no restrictions on the number or maximum length of downloaded videos.