Up next in 10
Ensuring Quality in DevOps Culture
0 views
Aug 6, 2025
Join Sagar Mahendrakar, Software Quality Engineer at Red Hat, as he explores the critical role of Quality Assurance (QA) for achieving superior software performance and reliability. In this session, Sagar will address the cultural and organizational challenges of embedding QA practices within DevOps, emphasizing the need to foster collaboration, dismantle silos, and cultivate a culture of continuous improvement. He will also highlight the importance of toolchain integration and skills development to support effective QA processes. Learn the strategies to navigate these challenges and enhance software delivery in today's dynamic technology environments. 👉 Code Quality Conference 2024 https://codequalityconf.com/ 📺 CSharp TV - Dev Streaming Destination http://csharp.tv 🌎 C# Corner - Community of Software and Data Developers https://www.c-sharpcorner.com/ #CSharpTV #csharpcorner #CodeQualityConf
View Video Transcript
0:03
so hey hi everyone my name is Sagar
0:05
so hey hi everyone my name is Sagar
0:05
so hey hi everyone my name is Sagar mahindar and I am from India I hold a
0:08
mahindar and I am from India I hold a
0:08
mahindar and I am from India I hold a bachelor's degree and currently working
0:10
bachelor's degree and currently working
0:10
bachelor's degree and currently working with red hat I have almost five years of
0:13
with red hat I have almost five years of
0:13
with red hat I have almost five years of experience in a quality engineer role
0:15
experience in a quality engineer role
0:15
experience in a quality engineer role mostly I am responsible for bu task of
0:18
mostly I am responsible for bu task of
0:19
mostly I am responsible for bu task of project involvement in Sprint planning
0:20
project involvement in Sprint planning
0:21
project involvement in Sprint planning Sprint releases automating test cases
0:23
Sprint releases automating test cases
0:23
Sprint releases automating test cases integration it with cicd pipelines and
0:26
integration it with cicd pipelines and
0:26
integration it with cicd pipelines and to make sure that our uh product is bug
0:28
to make sure that our uh product is bug
0:28
to make sure that our uh product is bug free so today I will share one of my
0:31
free so today I will share one of my
0:31
free so today I will share one of my experience uh when I was working with a
0:33
experience uh when I was working with a
0:33
experience uh when I was working with a previous organization we used to follow
0:36
previous organization we used to follow
0:36
previous organization we used to follow waterfall methodology and uh because of
0:39
waterfall methodology and uh because of
0:39
waterfall methodology and uh because of uh because of this our development cycle
0:41
uh because of this our development cycle
0:41
uh because of this our development cycle was too long we Face uh some challenges
0:44
was too long we Face uh some challenges
0:44
was too long we Face uh some challenges like uh difficulty in uh accommodating
0:47
like uh difficulty in uh accommodating
0:47
like uh difficulty in uh accommodating change request because uh customer
0:49
change request because uh customer
0:49
change request because uh customer requirement keeps on uh changing with
0:51
requirement keeps on uh changing with
0:51
requirement keeps on uh changing with time it it was difficult to accommodate
0:54
time it it was difficult to accommodate
0:54
time it it was difficult to accommodate any change request after a requirement
0:56
any change request after a requirement
0:56
any change request after a requirement specific specification phase was
0:59
specific specification phase was
1:00
specific specification phase was complete also in the waterfall model
1:02
complete also in the waterfall model
1:02
complete also in the waterfall model testing is typically done towards the
1:05
testing is typically done towards the
1:05
testing is typically done towards the end of the development process that
1:07
end of the development process that
1:07
end of the development process that means this means that defects may not be
1:11
means this means that defects may not be
1:11
means this means that defects may not be discovered until the late until the late
1:14
discovered until the late until the late
1:14
discovered until the late until the late in the development process which can be
1:16
in the development process which can be
1:16
in the development process which can be expensive and time consuming to fix but
1:20
expensive and time consuming to fix but
1:20
expensive and time consuming to fix but uh when I join but when I joined rat
1:22
uh when I join but when I joined rat
1:23
uh when I join but when I joined rat where aile methology is used I got to
1:25
where aile methology is used I got to
1:25
where aile methology is used I got to know why agile is important for
1:27
know why agile is important for
1:27
know why agile is important for development and testing purposes
1:30
development and testing purposes
1:30
development and testing purposes and uh what makes it successful is uh de
1:33
and uh what makes it successful is uh de
1:33
and uh what makes it successful is uh de offs so let's start with the today's
1:35
offs so let's start with the today's
1:35
offs so let's start with the today's topic insuring quality with uh Insurance
1:38
topic insuring quality with uh Insurance
1:38
topic insuring quality with uh Insurance quality inops
1:39
quality inops
1:39
quality inops culture uh moving to next
1:42
culture uh moving to next
1:43
culture uh moving to next slide yeah just
1:47
yeah yeah so let's walk through from the
1:51
yeah yeah so let's walk through from the
1:51
yeah yeah so let's walk through from the agenda for the today's
1:53
agenda for the today's
1:53
agenda for the today's session uh we will start with the
1:55
session uh we will start with the
1:55
session uh we will start with the introduction for DS and their importance
1:59
introduction for DS and their importance
1:59
introduction for DS and their importance then uh we will learn the relationship
2:01
then uh we will learn the relationship
2:01
then uh we will learn the relationship between doops and the quality
2:02
between doops and the quality
2:02
between doops and the quality engineering moving further we will
2:04
engineering moving further we will
2:05
engineering moving further we will discuss the role of QE in doops and
2:08
discuss the role of QE in doops and
2:08
discuss the role of QE in doops and their responsibilities in brief then uh
2:10
their responsibilities in brief then uh
2:10
their responsibilities in brief then uh we can discuss more about challenges
2:12
we can discuss more about challenges
2:12
we can discuss more about challenges that may QE face while working with
2:15
that may QE face while working with
2:15
that may QE face while working with doops we will have some deep knowledge
2:18
doops we will have some deep knowledge
2:18
doops we will have some deep knowledge about uh tool Chell integration and uh
2:21
about uh tool Chell integration and uh
2:21
about uh tool Chell integration and uh their importance at last we will discuss
2:24
their importance at last we will discuss
2:24
their importance at last we will discuss more about skills required for QE to
2:27
more about skills required for QE to
2:27
more about skills required for QE to work with the doops and uh then we we
2:30
work with the doops and uh then we we
2:30
work with the doops and uh then we we can have a conclusion in the QA session
2:33
can have a conclusion in the QA session
2:33
can have a conclusion in the QA session so moving to the first
2:35
so moving to the first
2:35
so moving to the first slide
2:36
slide
2:36
slide yeah so what is doops doops combines
2:40
yeah so what is doops doops combines
2:40
yeah so what is doops doops combines development and operation to increase
2:42
development and operation to increase
2:42
development and operation to increase the efficiency speed and the security of
2:45
the efficiency speed and the security of
2:45
the efficiency speed and the security of software development and uh delivery
2:47
software development and uh delivery
2:47
software development and uh delivery compared to traditional processes it
2:49
compared to traditional processes it
2:49
compared to traditional processes it also allows organization to serve their
2:52
also allows organization to serve their
2:52
also allows organization to serve their customers better and uh compete more
2:54
customers better and uh compete more
2:54
customers better and uh compete more strongly in the market in simple words
2:57
strongly in the market in simple words
2:57
strongly in the market in simple words uh doops can be defined as a alignment
3:00
uh doops can be defined as a alignment
3:00
uh doops can be defined as a alignment of development and it operation with a
3:02
of development and it operation with a
3:02
of development and it operation with a better communication and collaboration
3:06
better communication and collaboration
3:06
better communication and collaboration uh there are few reason that why jobs is
3:08
uh there are few reason that why jobs is
3:08
uh there are few reason that why jobs is necessary for modern businesses I have
3:11
necessary for modern businesses I have
3:11
necessary for modern businesses I have listed a few of them here like uh first
3:13
listed a few of them here like uh first
3:13
listed a few of them here like uh first one is short development Cycles early
3:16
one is short development Cycles early
3:16
one is short development Cycles early error detection uh reduces operational
3:19
error detection uh reduces operational
3:19
error detection uh reduces operational cost improves customer satisfaction so
3:21
cost improves customer satisfaction so
3:21
cost improves customer satisfaction so starting with the short development
3:23
starting with the short development
3:23
starting with the short development Cycles uh devops allows developers to
3:26
Cycles uh devops allows developers to
3:26
Cycles uh devops allows developers to release their product much quicker
3:28
release their product much quicker
3:28
release their product much quicker because uh they no longer have to wait
3:30
because uh they no longer have to wait
3:30
because uh they no longer have to wait for approval from other teams before
3:33
for approval from other teams before
3:33
for approval from other teams before releasing a new software versions
3:36
releasing a new software versions
3:36
releasing a new software versions instead they can release new version as
3:38
instead they can release new version as
3:38
instead they can release new version as soon as uh they are ready for testing
3:41
soon as uh they are ready for testing
3:41
soon as uh they are ready for testing which means uh which means that bugs can
3:44
which means uh which means that bugs can
3:44
which means uh which means that bugs can be caught much earlier in the process
3:47
be caught much earlier in the process
3:47
be caught much earlier in the process and fix before the they become uh
3:50
and fix before the they become uh
3:50
and fix before the they become uh significant issues uh second one early
3:53
significant issues uh second one early
3:53
significant issues uh second one early error detection when teams work together
3:56
error detection when teams work together
3:56
error detection when teams work together on Project there is more opportunity
3:58
on Project there is more opportunity
3:58
on Project there is more opportunity there is more opportunity for errors
4:00
there is more opportunity for errors
4:00
there is more opportunity for errors then a team working with the uh then A
4:03
then a team working with the uh then A
4:04
then a team working with the uh then A Team Works separately from another on
4:06
Team Works separately from another on
4:06
Team Works separately from another on the same project uh in a de of
4:08
the same project uh in a de of
4:08
the same project uh in a de of environment when one teams when one team
4:11
environment when one teams when one team
4:11
environment when one teams when one team makes an error in coding or testing the
4:15
makes an error in coding or testing the
4:15
makes an error in coding or testing the another team can detect it immediately
4:17
another team can detect it immediately
4:17
another team can detect it immediately and fix it before it causes any damage
4:20
and fix it before it causes any damage
4:20
and fix it before it causes any damage introduction it leads to higher quality
4:23
introduction it leads to higher quality
4:23
introduction it leads to higher quality products and a fewer problem down the
4:26
products and a fewer problem down the
4:26
products and a fewer problem down the road uh third one is reduces operational
4:29
road uh third one is reduces operational
4:29
road uh third one is reduces operational cost uh it's hard for business to keep
4:32
cost uh it's hard for business to keep
4:32
cost uh it's hard for business to keep up with the pace of Technology use if
4:35
up with the pace of Technology use if
4:36
up with the pace of Technology use if you are not keeping up you might as well
4:38
you are not keeping up you might as well
4:38
you are not keeping up you might as well close up your shop because your
4:40
close up your shop because your
4:40
close up your shop because your competitors will leave you in the dust
4:44
competitors will leave you in the dust
4:44
competitors will leave you in the dust one of the biggest reason why do is so
4:46
one of the biggest reason why do is so
4:46
one of the biggest reason why do is so important uh is so important because it
4:50
important uh is so important because it
4:50
important uh is so important because it helps companies lower operational cost
4:53
helps companies lower operational cost
4:53
helps companies lower operational cost by increasing efficiency which means
4:56
by increasing efficiency which means
4:56
by increasing efficiency which means they can spend less on uh support staff
4:59
they can spend less on uh support staff
4:59
they can spend less on uh support staff servers uh employers and other resources
5:02
servers uh employers and other resources
5:02
servers uh employers and other resources while um maintaining their competitive
5:05
while um maintaining their competitive
5:05
while um maintaining their competitive age fourth one is uh improves uh
5:08
age fourth one is uh improves uh
5:08
age fourth one is uh improves uh customer satisfaction one of the most
5:11
customer satisfaction one of the most
5:11
customer satisfaction one of the most important aspect of any business is is
5:14
important aspect of any business is is
5:14
important aspect of any business is is keeping your uh is keeping your customer
5:16
keeping your uh is keeping your customer
5:16
keeping your uh is keeping your customer happy uh there is no better way uh to do
5:19
happy uh there is no better way uh to do
5:19
happy uh there is no better way uh to do this than by providing excellent
5:21
this than by providing excellent
5:21
this than by providing excellent customer service which can be difficult
5:24
customer service which can be difficult
5:24
customer service which can be difficult for uh some companies dos can help make
5:28
for uh some companies dos can help make
5:28
for uh some companies dos can help make this easier for us and our team
5:31
this easier for us and our team
5:32
this easier for us and our team integrating our development team with
5:34
integrating our development team with
5:34
integrating our development team with our operation team can create a seamless
5:37
our operation team can create a seamless
5:37
our operation team can create a seamless experience for both customers and uh
5:39
experience for both customers and uh
5:39
experience for both customers and uh internal uh customers and internal
5:41
internal uh customers and internal
5:41
internal uh customers and internal employees it will also increase customer
5:44
employees it will also increase customer
5:44
employees it will also increase customer satisfaction because uh they don't have
5:46
satisfaction because uh they don't have
5:46
satisfaction because uh they don't have to wait long for their uh request to be
5:49
to wait long for their uh request to be
5:49
to wait long for their uh request to be answered it will also keep things
5:52
answered it will also keep things
5:52
answered it will also keep things running smoothly within our organization
5:55
running smoothly within our organization
5:55
running smoothly within our organization because everyone's uh know what uh they
5:58
because everyone's uh know what uh they
5:58
because everyone's uh know what uh they need to do next
6:01
need to do next
6:01
need to do next hope uh we got some Basics and uh
6:03
hope uh we got some Basics and uh
6:03
hope uh we got some Basics and uh importance of the de Ops now moving to
6:06
importance of the de Ops now moving to
6:06
importance of the de Ops now moving to next
6:08
slide yeah so now we will uh discuss
6:12
slide yeah so now we will uh discuss
6:12
slide yeah so now we will uh discuss relationship between QE and uh where
6:15
relationship between QE and uh where
6:15
relationship between QE and uh where exactly QA fits so de become so popular
6:18
exactly QA fits so de become so popular
6:18
exactly QA fits so de become so popular with the implementation of agile but
6:20
with the implementation of agile but
6:20
with the implementation of agile but where does QA fit in the world of
6:23
where does QA fit in the world of
6:23
where does QA fit in the world of continuous integration dominated by
6:26
continuous integration dominated by
6:26
continuous integration dominated by doops well pretty much almost in every
6:29
doops well pretty much almost in every
6:29
doops well pretty much almost in every release a quality analyst is required to
6:32
release a quality analyst is required to
6:32
release a quality analyst is required to assure the robustness of the product
6:35
assure the robustness of the product
6:35
assure the robustness of the product especially in the world of doops where
6:38
especially in the world of doops where
6:38
especially in the world of doops where updates take place in an application
6:40
updates take place in an application
6:40
updates take place in an application almost on uh almost on weekly
6:43
almost on uh almost on weekly
6:43
almost on uh almost on weekly basis with with so many frequent changes
6:47
basis with with so many frequent changes
6:47
basis with with so many frequent changes uh taking place outages look to be very
6:50
uh taking place outages look to be very
6:50
uh taking place outages look to be very common and outages are supposed to break
6:52
common and outages are supposed to break
6:52
common and outages are supposed to break the life of the developer and the
6:54
the life of the developer and the
6:54
the life of the developer and the manager everyone needs everyone needs a
6:57
manager everyone needs everyone needs a
6:57
manager everyone needs everyone needs a a quick hot fix when when a service of a
7:00
a quick hot fix when when a service of a
7:00
a quick hot fix when when a service of a product goes south affecting more than a
7:02
product goes south affecting more than a
7:02
product goes south affecting more than a single customer but an immediate fix
7:05
single customer but an immediate fix
7:05
single customer but an immediate fix needs to be thoroughly tested before it
7:07
needs to be thoroughly tested before it
7:07
needs to be thoroughly tested before it gets migrated in
7:09
gets migrated in
7:09
gets migrated in production developers and product
7:11
production developers and product
7:11
production developers and product manager would want the job to be done in
7:13
manager would want the job to be done in
7:13
manager would want the job to be done in a we this this is where QA needs needs
7:17
a we this this is where QA needs needs
7:17
a we this this is where QA needs needs to step up and uh take the
7:19
to step up and uh take the
7:19
to step up and uh take the responsibility of evaluating whether the
7:21
responsibility of evaluating whether the
7:21
responsibility of evaluating whether the immediate fix for an outage does not end
7:24
immediate fix for an outage does not end
7:24
immediate fix for an outage does not end up affecting any other functionality or
7:27
up affecting any other functionality or
7:27
up affecting any other functionality or it shouldn't be breaking the existing
7:28
it shouldn't be breaking the existing
7:28
it shouldn't be breaking the existing functionality
7:30
functionality
7:30
functionality so just as much as developer is needed
7:32
so just as much as developer is needed
7:32
so just as much as developer is needed to get rid of an outage by quick fix
7:35
to get rid of an outage by quick fix
7:35
to get rid of an outage by quick fix quality analyst is needed to prevent
7:38
quality analyst is needed to prevent
7:38
quality analyst is needed to prevent future outages F future outages to many
7:42
future outages F future outages to many
7:42
future outages F future outages to many extent as
7:43
extent as
7:43
extent as possible uh yeah so this was the
7:46
possible uh yeah so this was the
7:46
possible uh yeah so this was the relationship between the QE and the Dos
7:49
relationship between the QE and the Dos
7:49
relationship between the QE and the Dos moving to next
7:50
moving to next
7:50
moving to next slide yeah challenges faed by QE teams
7:54
slide yeah challenges faed by QE teams
7:54
slide yeah challenges faed by QE teams in a DS so there are several challenges
7:57
in a DS so there are several challenges
7:57
in a DS so there are several challenges may arise due to the fundamental changes
7:59
may arise due to the fundamental changes
7:59
may arise due to the fundamental changes in workflow collaboration and Technology
8:02
in workflow collaboration and Technology
8:02
in workflow collaboration and Technology use that such as integration
8:05
use that such as integration
8:05
use that such as integration ints quality Engineering in a doops
8:08
ints quality Engineering in a doops
8:08
ints quality Engineering in a doops environment it is not just about
8:11
environment it is not just about
8:11
environment it is not just about ensuring the quality of the software but
8:13
ensuring the quality of the software but
8:13
ensuring the quality of the software but also about but also about enhancing the
8:16
also about but also about enhancing the
8:16
also about but also about enhancing the processes that uh led to the development
8:19
processes that uh led to the development
8:19
processes that uh led to the development of high quality software
8:22
of high quality software
8:22
of high quality software products so here I will discuss some of
8:24
products so here I will discuss some of
8:25
products so here I will discuss some of the main challenges uh quality engineer
8:27
the main challenges uh quality engineer
8:27
the main challenges uh quality engineer might face uh I have listed few of them
8:29
might face uh I have listed few of them
8:29
might face uh I have listed few of them like uh shift left speed versus quality
8:32
like uh shift left speed versus quality
8:32
like uh shift left speed versus quality tradeoff automate testing expertise
8:35
tradeoff automate testing expertise
8:35
tradeoff automate testing expertise keeping up the changes so starting with
8:38
keeping up the changes so starting with
8:38
keeping up the changes so starting with the shift lift and continuous testing
8:40
the shift lift and continuous testing
8:40
the shift lift and continuous testing Dev emphasize shifting lift which means
8:43
Dev emphasize shifting lift which means
8:43
Dev emphasize shifting lift which means testing early and often in the
8:45
testing early and often in the
8:45
testing early and often in the development cycle this requires the QV
8:47
development cycle this requires the QV
8:47
development cycle this requires the QV team to integrate uh testing seamlessly
8:50
team to integrate uh testing seamlessly
8:50
team to integrate uh testing seamlessly into the daily workflows of development
8:52
into the daily workflows of development
8:53
into the daily workflows of development which can be a significant change from
8:54
which can be a significant change from
8:55
which can be a significant change from uh traditional models where testing was
8:57
uh traditional models where testing was
8:57
uh traditional models where testing was a distinct a distinct phase and also QB
9:00
a distinct a distinct phase and also QB
9:00
a distinct a distinct phase and also QB teams must adapt by developing automate
9:02
teams must adapt by developing automate
9:02
teams must adapt by developing automate test case that can run uh that can run
9:05
test case that can run uh that can run
9:05
test case that can run uh that can run effectively at every stage of a cicd
9:09
effectively at every stage of a cicd
9:09
effectively at every stage of a cicd pipeline uh second one is a speed versus
9:11
pipeline uh second one is a speed versus
9:12
pipeline uh second one is a speed versus trade uh tradeoff speed versus quality
9:15
trade uh tradeoff speed versus quality
9:15
trade uh tradeoff speed versus quality tradeoff uh deos prioritize speed and
9:18
tradeoff uh deos prioritize speed and
9:18
tradeoff uh deos prioritize speed and efficiency in delivering updates and new
9:20
efficiency in delivering updates and new
9:20
efficiency in delivering updates and new feature QE team are challenge to uh to
9:23
feature QE team are challenge to uh to
9:24
feature QE team are challenge to uh to maintain the high standard of quality
9:26
maintain the high standard of quality
9:26
maintain the high standard of quality without uh slowing down
9:29
without uh slowing down
9:29
without uh slowing down this can sometimes create a tension as
9:31
this can sometimes create a tension as
9:31
this can sometimes create a tension as the drive for Rapid releases May
9:33
the drive for Rapid releases May
9:33
the drive for Rapid releases May compromise the thoroughness of
9:36
compromise the thoroughness of
9:36
compromise the thoroughness of testing third one is automated testing
9:39
testing third one is automated testing
9:39
testing third one is automated testing expertise with the emphasis on
9:41
expertise with the emphasis on
9:41
expertise with the emphasis on Automation in De offs QV team must
9:43
Automation in De offs QV team must
9:43
Automation in De offs QV team must possess strong skills in automation
9:45
possess strong skills in automation
9:46
possess strong skills in automation testing this includes the ability to
9:48
testing this includes the ability to
9:48
testing this includes the ability to write maintain and understand the
9:50
write maintain and understand the
9:50
write maintain and understand the automate testing scripts and framework
9:53
automate testing scripts and framework
9:53
automate testing scripts and framework developing this expertise required time
9:56
developing this expertise required time
9:56
developing this expertise required time and training which can be a challenging
9:58
and training which can be a challenging
9:58
and training which can be a challenging especially in the fast phase
10:01
especially in the fast phase
10:01
especially in the fast phase environment keeping up the changes in a
10:04
environment keeping up the changes in a
10:04
environment keeping up the changes in a de of culture changes occur rapidly and
10:06
de of culture changes occur rapidly and
10:06
de of culture changes occur rapidly and frequently QB teams must keep up with
10:09
frequently QB teams must keep up with
10:09
frequently QB teams must keep up with these changes in both the software been
10:12
these changes in both the software been
10:12
these changes in both the software been develop and the technology used to
10:14
develop and the technology used to
10:14
develop and the technology used to develop and test it this continuous uh
10:17
develop and test it this continuous uh
10:18
develop and test it this continuous uh learning and adaption can be
10:21
learning and adaption can be
10:21
learning and adaption can be demanding um yeah so this were the
10:24
demanding um yeah so this were the
10:24
demanding um yeah so this were the challenges faced by the QE moving to
10:27
challenges faced by the QE moving to
10:27
challenges faced by the QE moving to next slide yeah so roles and
10:30
next slide yeah so roles and
10:30
next slide yeah so roles and responsibilities of QA and doops so yeah
10:34
responsibilities of QA and doops so yeah
10:34
responsibilities of QA and doops so yeah the quality engineer role is more
10:36
the quality engineer role is more
10:36
the quality engineer role is more demanding than QA was as it is more
10:39
demanding than QA was as it is more
10:39
demanding than QA was as it is more fundamentally focused on quality the QA
10:42
fundamentally focused on quality the QA
10:42
fundamentally focused on quality the QA role demands that uh you have you have
10:45
role demands that uh you have you have
10:45
role demands that uh you have you have expertise in all aspect of uh devs which
10:48
expertise in all aspect of uh devs which
10:48
expertise in all aspect of uh devs which can uh directly which can uh which can
10:52
can uh directly which can uh which can
10:52
can uh directly which can uh which can directly uh or indirectly related to
10:55
directly uh or indirectly related to
10:55
directly uh or indirectly related to product quality including uh including
10:58
product quality including uh including
10:58
product quality including uh including software test in uh automation testing
11:01
software test in uh automation testing
11:01
software test in uh automation testing uh aile processes cicd and Etc apart
11:05
uh aile processes cicd and Etc apart
11:05
uh aile processes cicd and Etc apart from this uh quality engineering
11:07
from this uh quality engineering
11:07
from this uh quality engineering personal should also should also have a
11:10
personal should also should also have a
11:10
personal should also should also have a good knowledge of design techniques uh
11:12
good knowledge of design techniques uh
11:12
good knowledge of design techniques uh the technology stack delivery processes
11:15
the technology stack delivery processes
11:15
the technology stack delivery processes Etc uh let's take an example let's
11:19
Etc uh let's take an example let's
11:19
Etc uh let's take an example let's understand the role of a tester in doops
11:21
understand the role of a tester in doops
11:21
understand the role of a tester in doops through an example suppose a software
11:25
through an example suppose a software
11:25
through an example suppose a software suppose a software company is working on
11:27
suppose a software company is working on
11:27
suppose a software company is working on a mobile application software the
11:29
a mobile application software the
11:29
a mobile application software the development teams adds new feature
11:31
development teams adds new feature
11:31
development teams adds new feature constantly and frequently and uh meets
11:34
constantly and frequently and uh meets
11:34
constantly and frequently and uh meets the user demand testers are essential in
11:37
the user demand testers are essential in
11:37
the user demand testers are essential in t section like uh participating in a
11:39
t section like uh participating in a
11:39
t section like uh participating in a project planning and collaborating
11:41
project planning and collaborating
11:41
project planning and collaborating closely with the product owners and the
11:43
closely with the product owners and the
11:43
closely with the product owners and the developers by this they understand the
11:45
developers by this they understand the
11:46
developers by this they understand the mobile application functionality and uh
11:48
mobile application functionality and uh
11:48
mobile application functionality and uh user needs next the tester develops
11:51
user needs next the tester develops
11:51
user needs next the tester develops automate scripts using a testing tools
11:54
automate scripts using a testing tools
11:54
automate scripts using a testing tools further integrating it with cicd
11:56
further integrating it with cicd
11:56
further integrating it with cicd pipelines also tester runs a different
11:59
pipelines also tester runs a different
11:59
pipelines also tester runs a different test cases of various mobile condition
12:01
test cases of various mobile condition
12:01
test cases of various mobile condition to judge the performance of the
12:03
to judge the performance of the
12:03
to judge the performance of the application on various machines and and
12:05
application on various machines and and
12:05
application on various machines and and various environments testers even
12:08
various environments testers even
12:08
various environments testers even conduct security test to identify
12:11
conduct security test to identify
12:11
conduct security test to identify whether there is a data leakage risk or
12:13
whether there is a data leakage risk or
12:13
whether there is a data leakage risk or not so there are some common roles and
12:16
not so there are some common roles and
12:16
not so there are some common roles and responsibility that QA should perform in
12:19
responsibility that QA should perform in
12:19
responsibility that QA should perform in a doops like a QA should aim to detect a
12:23
a doops like a QA should aim to detect a
12:23
a doops like a QA should aim to detect a bug at the earliest point in the cycle
12:25
bug at the earliest point in the cycle
12:25
bug at the earliest point in the cycle and uh also protect uh and also prevent
12:28
and uh also protect uh and also prevent
12:28
and uh also protect uh and also prevent potential bugs from reappearing in the
12:30
potential bugs from reappearing in the
12:30
potential bugs from reappearing in the production environment Q should not
12:33
production environment Q should not
12:33
production environment Q should not limit their role to only finding and
12:35
limit their role to only finding and
12:35
limit their role to only finding and preventing defects but uh should also
12:37
preventing defects but uh should also
12:37
preventing defects but uh should also highlight problems in the processes and
12:41
highlight problems in the processes and
12:41
highlight problems in the processes and recommended changes wherever necessary
12:43
recommended changes wherever necessary
12:43
recommended changes wherever necessary this practice is only possible uh if QA
12:46
this practice is only possible uh if QA
12:46
this practice is only possible uh if QA takes ownership of the improvement
12:48
takes ownership of the improvement
12:48
takes ownership of the improvement process in doops QA should uh make sure
12:52
process in doops QA should uh make sure
12:52
process in doops QA should uh make sure all environment required for testing
12:54
all environment required for testing
12:54
all environment required for testing should be standardized and deplo
12:56
should be standardized and deplo
12:56
should be standardized and deplo deployment should be
12:58
deployment should be
12:58
deployment should be automated there is no room for uh manual
13:00
automated there is no room for uh manual
13:01
automated there is no room for uh manual testing collaborates with developers uh
13:03
testing collaborates with developers uh
13:03
testing collaborates with developers uh throughout development phase
13:05
throughout development phase
13:05
throughout development phase contributing ideas and understanding
13:07
contributing ideas and understanding
13:07
contributing ideas and understanding future needs it help us to get fast uh
13:11
future needs it help us to get fast uh
13:11
future needs it help us to get fast uh fast and immediate feedback this uh this
13:14
fast and immediate feedback this uh this
13:14
fast and immediate feedback this uh this fast feedback loop is essential for
13:16
fast feedback loop is essential for
13:16
fast feedback loop is essential for determining and resolving issues early
13:19
determining and resolving issues early
13:19
determining and resolving issues early in the development phase so this were
13:22
in the development phase so this were
13:22
in the development phase so this were some of the roles and responsibility of
13:24
some of the roles and responsibility of
13:24
some of the roles and responsibility of QA in a
13:26
QA in a
13:26
QA in a deop uh now moving to to next slide yeah
13:31
deop uh now moving to to next slide yeah
13:31
deop uh now moving to to next slide yeah tool chain
13:32
tool chain
13:32
tool chain integration so what is tool chain a tool
13:35
integration so what is tool chain a tool
13:35
integration so what is tool chain a tool chain is a collection of tools and
13:36
chain is a collection of tools and
13:36
chain is a collection of tools and technologies that enable development and
13:39
technologies that enable development and
13:39
technologies that enable development and operation teams to collaborate
13:41
operation teams to collaborate
13:41
operation teams to collaborate throughout the entire software uh phase
13:45
throughout the entire software uh phase
13:45
throughout the entire software uh phase de fundamental such as a continuous
13:47
de fundamental such as a continuous
13:47
de fundamental such as a continuous integration continuous delivery
13:49
integration continuous delivery
13:49
integration continuous delivery continuous deployment Automation and
13:51
continuous deployment Automation and
13:51
continuous deployment Automation and collaboration tool chain integration in
13:53
collaboration tool chain integration in
13:53
collaboration tool chain integration in doops and QV is is crucial for achieving
13:57
doops and QV is is crucial for achieving
13:57
doops and QV is is crucial for achieving the seamless automation and
13:59
the seamless automation and
13:59
the seamless automation and collaboration required to support rapid
14:02
collaboration required to support rapid
14:02
collaboration required to support rapid Reliable Software releases a well
14:05
Reliable Software releases a well
14:05
Reliable Software releases a well integrated tool chain allows for a
14:08
integrated tool chain allows for a
14:08
integrated tool chain allows for a continuous uh deployment development
14:11
continuous uh deployment development
14:11
continuous uh deployment development testings which are the cornerstones of
14:13
testings which are the cornerstones of
14:13
testings which are the cornerstones of the de
14:14
the de
14:14
the de philosophy here is a detailed look at uh
14:17
philosophy here is a detailed look at uh
14:17
philosophy here is a detailed look at uh the importance of tool chain integration
14:20
the importance of tool chain integration
14:20
the importance of tool chain integration uh let's get uh brief in the importance
14:23
uh let's get uh brief in the importance
14:23
uh let's get uh brief in the importance of tool chain integration so I have
14:25
of tool chain integration so I have
14:25
of tool chain integration so I have listed uh some of them uh streamlined
14:28
listed uh some of them uh streamlined
14:28
listed uh some of them uh streamlined workflow at
14:29
workflow at
14:29
workflow at enhance collaboration consistency and
14:32
enhance collaboration consistency and
14:32
enhance collaboration consistency and standardization realtime feedback and
14:34
standardization realtime feedback and
14:35
standardization realtime feedback and the metrics so starting with the
14:37
the metrics so starting with the
14:37
the metrics so starting with the Streamline workflow automation
14:39
Streamline workflow automation
14:39
Streamline workflow automation integration of tools in a doops
14:41
integration of tools in a doops
14:41
integration of tools in a doops environment helps in creating a seamless
14:44
environment helps in creating a seamless
14:44
environment helps in creating a seamless workflow for a developer operation teams
14:46
workflow for a developer operation teams
14:46
workflow for a developer operation teams and a quality engineer each stage each
14:49
and a quality engineer each stage each
14:49
and a quality engineer each stage each stage of the software development uh
14:52
stage of the software development uh
14:52
stage of the software development uh life cycles from planning and coding to
14:55
life cycles from planning and coding to
14:55
life cycles from planning and coding to testing deployments and monitor can be
14:57
testing deployments and monitor can be
14:57
testing deployments and monitor can be automate this this automation reduces
15:00
automate this this automation reduces
15:00
automate this this automation reduces the manual hands off between uh teams
15:03
the manual hands off between uh teams
15:03
the manual hands off between uh teams minimizes error and uh speed up the
15:05
minimizes error and uh speed up the
15:05
minimizes error and uh speed up the process of the software
15:07
process of the software
15:07
process of the software delivery enhance collaboration tool CH
15:10
delivery enhance collaboration tool CH
15:10
delivery enhance collaboration tool CH integration uh facilate better
15:13
integration uh facilate better
15:13
integration uh facilate better communication and collaboration among
15:15
communication and collaboration among
15:15
communication and collaboration among cross functional teams tools such as uh
15:17
cross functional teams tools such as uh
15:17
cross functional teams tools such as uh chatbot integration with the issue
15:19
chatbot integration with the issue
15:19
chatbot integration with the issue tracking system can automate status
15:22
tracking system can automate status
15:22
tracking system can automate status updates and alerts this uh this keeps
15:25
updates and alerts this uh this keeps
15:25
updates and alerts this uh this keeps everyone in the loop and uh make it
15:27
everyone in the loop and uh make it
15:27
everyone in the loop and uh make it easier for for the team members to react
15:29
easier for for the team members to react
15:30
easier for for the team members to react quickly to development or operational
15:32
quickly to development or operational
15:32
quickly to development or operational issues ensuring that everyone uh from
15:34
issues ensuring that everyone uh from
15:34
issues ensuring that everyone uh from the unified platform with access to the
15:38
the unified platform with access to the
15:38
the unified platform with access to the real-time data consistency and
15:41
real-time data consistency and
15:41
real-time data consistency and standardization integrated tools help
15:43
standardization integrated tools help
15:43
standardization integrated tools help standardize processes across the
15:45
standardize processes across the
15:45
standardize processes across the development testing and the deployment
15:47
development testing and the deployment
15:47
development testing and the deployment phases this standardization is crucial
15:50
phases this standardization is crucial
15:50
phases this standardization is crucial for uh maintaining uh consistency in how
15:53
for uh maintaining uh consistency in how
15:53
for uh maintaining uh consistency in how software is developed tested and uh
15:56
software is developed tested and uh
15:56
software is developed tested and uh released which in turn helps in managing
15:59
released which in turn helps in managing
15:59
released which in turn helps in managing uh complex systems and uh reducing
16:01
uh complex systems and uh reducing
16:01
uh complex systems and uh reducing reducing the unexpected behavior of uh
16:05
reducing the unexpected behavior of uh
16:05
reducing the unexpected behavior of uh discre discrepancy in a production
16:07
discre discrepancy in a production
16:07
discre discrepancy in a production environment realtime
16:10
environment realtime
16:10
environment realtime feedback integrated uh tools provide
16:13
feedback integrated uh tools provide
16:13
feedback integrated uh tools provide continuous feedback and uh detailed
16:15
continuous feedback and uh detailed
16:15
continuous feedback and uh detailed metrics about every aspect of the
16:17
metrics about every aspect of the
16:17
metrics about every aspect of the development life cycle for instance uh
16:20
development life cycle for instance uh
16:20
development life cycle for instance uh Dash uh for instance dashboard tools
16:23
Dash uh for instance dashboard tools
16:23
Dash uh for instance dashboard tools that integrate with CI server testing FR
16:26
that integrate with CI server testing FR
16:26
that integrate with CI server testing FR Frameworks and deployment tools can uh
16:28
Frameworks and deployment tools can uh
16:28
Frameworks and deployment tools can uh provide real time Insight real time
16:31
provide real time Insight real time
16:31
provide real time Insight real time insight to the into the code quality uh
16:35
insight to the into the code quality uh
16:35
insight to the into the code quality uh test coverage uh build history and uh
16:38
test coverage uh build history and uh
16:38
test coverage uh build history and uh deployment
16:39
deployment
16:39
deployment frequency this data is vital for making
16:43
frequency this data is vital for making
16:43
frequency this data is vital for making informed decision about the product and
16:45
informed decision about the product and
16:46
informed decision about the product and uh process Improvement for Quality
16:48
uh process Improvement for Quality
16:48
uh process Improvement for Quality engineering integration of tools like a
16:51
engineering integration of tools like a
16:51
engineering integration of tools like a source control build servers deployment
16:54
source control build servers deployment
16:54
source control build servers deployment mechanism and uh testing uh Frameworks
16:57
mechanism and uh testing uh Frameworks
16:57
mechanism and uh testing uh Frameworks means they can Ensure comprehensive
16:59
means they can Ensure comprehensive
16:59
means they can Ensure comprehensive quality checks are performed
17:02
quality checks are performed
17:02
quality checks are performed automatically this integrated approach
17:04
automatically this integrated approach
17:04
automatically this integrated approach helps QV teams to implement and
17:07
helps QV teams to implement and
17:07
helps QV teams to implement and Implement Advanced
17:09
Implement Advanced
17:09
Implement Advanced testing strategies such as a shift LIF
17:12
testing strategies such as a shift LIF
17:12
testing strategies such as a shift LIF testing performance testing and security
17:14
testing performance testing and security
17:14
testing performance testing and security testing as a part of development
17:16
testing as a part of development
17:16
testing as a part of development pipeline rather than rather than as
17:19
pipeline rather than rather than as
17:19
pipeline rather than rather than as after thoughts rather than as after
17:23
after thoughts rather than as after
17:23
after thoughts rather than as after thought uh moving to the next slide yeah
17:27
thought uh moving to the next slide yeah
17:27
thought uh moving to the next slide yeah the skill required for the test
17:29
the skill required for the test
17:29
the skill required for the test in uh for testers in the I know there
17:32
in uh for testers in the I know there
17:32
in uh for testers in the I know there might be more skills required but uh as
17:36
might be more skills required but uh as
17:36
might be more skills required but uh as I know I listed few of them like uh
17:38
I know I listed few of them like uh
17:38
I know I listed few of them like uh knowledge of software testing knowledge
17:40
knowledge of software testing knowledge
17:40
knowledge of software testing knowledge of De technology collaboration abilities
17:44
of De technology collaboration abilities
17:44
of De technology collaboration abilities understanding of automation uh testing
17:45
understanding of automation uh testing
17:46
understanding of automation uh testing and the
17:46
and the
17:46
and the Frameworks
17:48
Frameworks
17:48
Frameworks so understanding software testing will
17:50
so understanding software testing will
17:50
so understanding software testing will enable you to spot and uh resolve
17:53
enable you to spot and uh resolve
17:53
enable you to spot and uh resolve software program uh program problems
17:55
software program uh program problems
17:56
software program uh program problems quickly knowledge of doops Technology is
17:59
quickly knowledge of doops Technology is
17:59
quickly knowledge of doops Technology is will enable us to organize and automate
18:02
will enable us to organize and automate
18:02
will enable us to organize and automate the software development and the testing
18:04
the software development and the testing
18:04
the software development and the testing processes one should have collaboration
18:06
processes one should have collaboration
18:06
processes one should have collaboration abilities with uh developers product
18:08
abilities with uh developers product
18:08
abilities with uh developers product owners or any uh team
18:11
owners or any uh team
18:11
owners or any uh team members understanding how to automate
18:14
members understanding how to automate
18:14
members understanding how to automate automate testing and uh deploy code
18:16
automate testing and uh deploy code
18:16
automate testing and uh deploy code updates regularly is important he should
18:19
updates regularly is important he should
18:19
updates regularly is important he should know what is uh cicd pipelines and the
18:22
know what is uh cicd pipelines and the
18:22
know what is uh cicd pipelines and the continuous uh deployment and continuous
18:25
continuous uh deployment and continuous
18:25
continuous uh deployment and continuous uh development phases it it would be it
18:28
uh development phases it it would be it
18:28
uh development phases it it would be it would be better as a tester to have some
18:31
would be better as a tester to have some
18:31
would be better as a tester to have some knowledge in a
18:32
knowledge in a
18:32
knowledge in a doops so this was the skills required
18:35
doops so this was the skills required
18:35
doops so this was the skills required for the testers uh moving to last slide
18:39
for the testers uh moving to last slide
18:39
for the testers uh moving to last slide Yeah so basically this is the conclusion
18:42
Yeah so basically this is the conclusion
18:42
Yeah so basically this is the conclusion uh slide and the evolution of the QA the
18:45
uh slide and the evolution of the QA the
18:45
uh slide and the evolution of the QA the impact of doops on a quality assurance
18:48
impact of doops on a quality assurance
18:48
impact of doops on a quality assurance testing strategies is trans is
18:50
testing strategies is trans is
18:50
testing strategies is trans is transformative by embracing a culture of
18:53
transformative by embracing a culture of
18:53
transformative by embracing a culture of collaboration Automation and continuous
18:56
collaboration Automation and continuous
18:56
collaboration Automation and continuous testing organization can achieve the
18:59
testing organization can achieve the
18:59
testing organization can achieve the delegate balance between speed and
19:00
delegate balance between speed and
19:00
delegate balance between speed and quality in a software development QA
19:03
quality in a software development QA
19:03
quality in a software development QA teams play patal role in the shift
19:07
teams play patal role in the shift
19:07
teams play patal role in the shift contributing to the creation of a
19:09
contributing to the creation of a
19:09
contributing to the creation of a resilient reliable and a high quality
19:12
resilient reliable and a high quality
19:12
resilient reliable and a high quality software is a dynamic DS environment uh
19:16
software is a dynamic DS environment uh
19:16
software is a dynamic DS environment uh as organization continue to evolve the
19:18
as organization continue to evolve the
19:18
as organization continue to evolve the integration of of De principle into QA
19:22
integration of of De principle into QA
19:22
integration of of De principle into QA testing strategies will be more
19:24
testing strategies will be more
19:24
testing strategies will be more fundamental to staying competitive in a
19:27
fundamental to staying competitive in a
19:27
fundamental to staying competitive in a Ever Changing land of
19:31
Ever Changing land of
19:31
Ever Changing land of Technology yeah so I think uh this
19:34
Technology yeah so I think uh this
19:34
Technology yeah so I think uh this session will be a productive one for as
19:36
session will be a productive one for as
19:36
session will be a productive one for as a tester and for a Dev team as well and
19:40
a tester and for a Dev team as well and
19:40
a tester and for a Dev team as well and uh this tester should try to implement
19:43
uh this tester should try to implement
19:43
uh this tester should try to implement this process in their team also for
19:46
this process in their team also for
19:46
this process in their team also for ensuring the quality of their
19:48
ensuring the quality of their
19:49
ensuring the quality of their product so that's it from my side so if
19:53
product so that's it from my side so if
19:53
product so that's it from my side so if you have any question you can come up
19:54
you have any question you can come up
19:54
you have any question you can come up with me or uh you can uh reach to my uh
19:58
with me or uh you can uh reach to my uh
19:58
with me or uh you can uh reach to my uh uh you can re on uh to me on LinkedIn so
20:01
uh you can re on uh to me on LinkedIn so
20:01
uh you can re on uh to me on LinkedIn so I can connect with you and we can
20:03
I can connect with you and we can
20:03
I can connect with you and we can discuss more about that yep
20:10
[Music]