0:10 [Music]
0:13 software continues to influence effect
0:16 and automate more areas of our lives so
0:18 testing software becomes more valuable
0:20 and important as we welcome new
0:23 applications and devices into a homes
0:25 and businesses to take command of
0:28 important tasks hey guys am Archana from
0:30 ed Eureka and I welcome you all to this
0:33 session on automation testing but before
0:35 we proceed let's go ahead and take a
0:36 look at topics that we will be talking
0:39 about today we will start the session by
0:41 discussing what is software testing and
0:44 why is it important then we will cover
0:46 the basics of automated software testing
0:48 like what it is why it's necessary for
0:51 the IT industry and how to make sense of
0:53 the technology behind it we will also
0:55 check out the differences between manual
0:58 testing and automation testing finally
0:59 we will end this session by discussing
1:02 popular automation testing tools so I
1:05 hope agenda was clear to you guys let's
1:06 get started there
1:10 on April 26 1994 aircraft named Airbus
1:13 a300 was completing the routine flight
1:15 and approach when just before landing at
1:18 Airport it crashed the crash killed
1:21 about 264 people and to date the
1:23 accident remains the deadliest accident
1:25 in the history of China Airlines
1:29 similarly on August 14 2003 shortly
1:30 after 2 p.m.
1:32 a high voltage power line in northern
1:35 Ohio brushed against some overgrown
1:37 trees and shut down completely
1:40 50 billion people lost power for up to 2
1:42 days in the biggest blackout in North
1:44 American history that did normally the
1:46 problem would have tripped an alarm in
1:48 the control room but due to software
1:50 glitches the alarm system failed in
1:53 April of 1999 there was failure of a 12
1:55 billion dollar military satellite launch
1:58 it was due to some sort of technical
2:00 issue and satellites guidance system
2:04 similarly in 1985 Canada's therac-25
2:07 radiation therapy machine malfunctioned
2:09 due to some software bug and delivered
2:11 lethal radiation to patients leaving
2:12 three people there and
2:15 injuring three others so now you might
2:17 be wondering why am i discussing all
2:20 this here right well all the incidents
2:22 that I mentioned just now happen because
2:25 of the software box software used here
2:28 was not tested before implementing every
2:31 system has software box it's impossible
2:33 to design and bring out a perfect
2:35 software product fundamentally the world
2:37 itself is imprecise and unpredictable
2:39 and all the software systems connect to
2:41 the real world and one or the other way
2:44 so software testing is very important
2:46 software testing basically is the
2:49 process of executing the software or an
2:51 application to find out if there are any
2:53 kind of bugs or some sort of errors and
2:55 as the name already suggests the
2:57 software testing means checking the
3:00 developed software for any mistakes and
3:02 problems in the initial design of
3:04 software so the incidents that we
3:07 discussed earlier are just few there are
3:09 many other fatal incidents that occur
3:11 due to lack of software testing so
3:14 software testing gives confidence in the
3:16 quality of final product it confirms
3:19 that the application has no errors in
3:21 the code it verifies how the user can
3:23 work with application and ensures that
3:26 the introduct is very easy to use it
3:28 also tells for the Box in the software
3:31 in the initial stages of development and
3:34 until the software is ready it confirms
3:35 that the application is able to operate
3:38 in all the required conditions and on
3:40 all supported operating systems or web
3:43 browsers correctly and safely so before
3:45 actually software goes public
3:47 programmers spend hovers trying to iron
3:49 out every little bug there is and
3:51 software and that is what we call
3:54 software testing testing is broadly
3:56 classified as manual testing and
3:59 automated testing so manual testing it's
4:02 pretty self-explanatory light testing of
4:04 a web application is done manually by
4:06 human action that's what we call manual
4:08 testing this means that someone actually
4:11 goes on a device to evaluate numerous
4:12 components including design
4:14 functionality and performance of
4:17 software so they click through multiple
4:19 elements or units of web application
4:21 without any support from tool or scrip
4:24 thorough testing is crucial to the
4:26 success of a software product if you
4:28 software doesn't work properly chances
4:30 are strong that most people won't buy it
4:32 or even use it at least not for long
4:35 even if they bite but testing to find
4:37 defects or some sort of bugs is very
4:39 time consuming expensive often
4:41 repetitive and subjective to human error
4:43 if you are using manual testing
4:46 so this is where automation testing
4:48 comes into picture automation testing
4:51 well its automated the buzzword
4:53 automation focuses on replacing manual
4:56 human activity with systems or devices
4:59 that enhance efficiency of software test
5:01 automation or usually referred as
5:03 automation testing uses different kind
5:06 of tools scripts and software to perform
5:08 test cases by repeating predefined
5:11 actions so by automating your software
5:13 testing activities you will definitely
5:16 get a competitive edge in the market so
5:18 let me give you some examples Amazon is
5:20 testing delivery drones that pick up
5:23 warehouse orders sorted by robots Google
5:26 is testing self-driving cars Starbucks
5:29 is testing kasia free stores dedicated
5:32 to mobile ordering and payment Facebook
5:34 is testing a brain-computer interface
5:36 that may one day translate thoughts into
5:39 digital text fascinating right there are
5:40 mundane versions of automation
5:43 technology behind all this testing
5:46 software automation testing companies
5:48 use automation technology to create the
5:50 software responsible for the products
5:52 and services causing all this hype about
5:54 automation testing when you actually
5:56 begin testing one of the primary
5:58 decisions that you'll have to make is if
6:00 to choose manual testing or automated
6:02 testing well neither of these options
6:04 are technically better or worse when
6:07 compared to each other factors like size
6:09 budget time allowance of the project
6:11 will certainly be factors that affect
6:13 which method will work best in the
6:15 situation so you should be aware of
6:17 distinct differences between manual
6:20 testing and automated testing so here we
6:22 go the first difference obviously the
6:24 definition which we discussed earlier in
6:26 manual testing test cases are executed
6:29 by human tester and software whereas
6:31 automation testing uses different kind
6:33 of automation tools and scripts to
6:36 execute test cases so let's get started
6:39 with other factors the first is rely
6:41 for a testing phase where duration is
6:43 very long there are high chances of an
6:45 undetected error when testing is
6:48 performed manually every time a small
6:49 defect is fixed the entire application
6:52 needs to be tested to ensure that any
6:54 other breakage is not occurring well the
6:56 process is tiling and boring
6:59 so testers often miss out critical
7:01 defects while performing repeated
7:03 testing it's a common human behavior
7:05 light therefore the accuracy and
7:07 reliability of manual testing is very
7:10 low automated testing on other hand is
7:13 more reliable tools are the scripts that
7:16 you use from the automated tests if the
7:18 script is properly written there is no
7:20 chance of missing a defect when the test
7:22 is executed over and over again and
7:24 obviously it's not boring as well for
7:26 the machine right when it comes to
7:29 reliability automated testing is highly
7:31 reliable then comes the time required to
7:34 perform the testing manual testing is
7:36 obviously time-consuming it takes up
7:38 human resources but when it comes to
7:40 automated testing its executed by
7:42 software tools and different kind of
7:44 scripts so it is significantly faster
7:47 when compared to manual testing next we
7:49 have when to use which kind of testing
7:52 manual testing is suitable when the test
7:54 cases are run once or twice therefore
7:56 there is no frequent repetition of test
7:58 cases and manual testing so two named
8:00 manual testing is suitable for
8:03 exploratory or usability and ad hoc
8:06 testing automated testing is suitable
8:07 when the test cases need to be run
8:10 repeatedly for a long duration of time
8:12 automation testing is suited for
8:14 regression testing performance testing
8:16 load testing or highly repeatable
8:19 functional test cases and next we have
8:22 performance and batch testing which is
8:24 not possible in manual testing you can
8:27 batch multiple test scripts in automated
8:29 testing performance tests like load
8:32 testing stress testing spike texting etc
8:34 have to be tested by an automation tool
8:37 compulsorily and software testing
8:39 process then we have investment costs
8:42 the cost of manual testing is usually
8:44 dependent upon the human resource
8:45 deployed in the testing during the
8:48 initial stages of testing the initial
8:50 investment in manual testing is
8:52 comparatively lower but the
8:54 written of investment is very low when
8:56 compared to automation testing when I
8:59 say written of investment I mean the
9:01 money that you own as in a venue at the
9:03 end of the software testing or after
9:05 selling the product is actually low and
9:07 compared to automation testing in long
9:09 run thatís but the cost of automated
9:11 testing is dependant upon testing tools
9:14 deployed for performing the tests but
9:15 the initial investment in automation
9:18 testing is usually higher though the
9:20 rigor of investment is better in long
9:23 run so when it comes to investment cause
9:25 initial investment manual testing is
9:27 much preferable but if you want to
9:29 perform testing for long run
9:31 then automation testing is much
9:34 preferable as the last criteria we have
9:37 human element manual testing allows
9:39 human observation right so you are
9:41 getting exact kind of feedback a person
9:42 would give you and that can be
9:45 invaluable being able to predict what
9:47 your users will or won't like thinks
9:49 that a computer can't give feedback on
9:52 ahead of time can influence your design
9:54 and make it much better from the bottom
9:57 up it improves the customers experience
9:59 but when it comes to automated testing
10:00 as there is no human observation
10:03 involved there is no guarantee of
10:05 positive customer experience so when it
10:08 comes to human element manual testing is
10:10 much better because you get to have a
10:12 nice experience since the humans are the
10:14 ones who are checking the software so
10:16 guys these are some defenses that you
10:17 should be aware of between manual
10:20 testing and automation testing so to
10:21 summarize what you've learnt in now
10:24 automation testing is Lord of advantages
10:26 over manual testing first of all it
10:29 saves lot of time and money it improves
10:31 test accuracy it increases the test
10:33 coverage as then you can perform tests
10:35 repetitively on different kind of
10:38 devices complex tests and boring tasks
10:40 are made very easy and comfortable it
10:43 increases efficiency and team morale you
10:45 no longer have to do the boring and
10:46 repetitive tasks
10:48 there's been no human errors obviously
10:50 it reduces maintenance cost of testing
10:53 it increases speed of executing tests
10:55 and many more advantages so in short
10:58 while manual testing is effective in
11:00 projects with multiple operating
11:02 environments and hardware configurations
11:04 automation testing is absolutely
11:06 essential today - sucks
11:08 fully deliver large-scale products that
11:11 need execution of repetitive and complex
11:13 test cases but it's impossible to
11:16 automate all testing so it is important
11:18 to determine what test cases should be
11:20 automated first so guys let's go ahead
11:22 and take a look at use cases where
11:24 automation testing have to be applied
11:26 because like I said you can't apply
11:28 automation everywhere first of all as
11:30 you guys know repetitive tasks are
11:32 primary candidates for automation take
11:34 an e-commerce site for an example it may
11:36 be testing entering in user credentials
11:39 multiple times consider the task that
11:41 you hate doing not only are the store's
11:43 boring to you but they're often the ones
11:46 where mistakes are made very commonly so
11:48 automate them and do something more fun
11:51 next capturing and sharing results is
11:53 obviously a critical part of successful
11:56 test strategy rather than manually
11:58 exporting your data crunching the
12:00 numbers and making petty graphs invest
12:02 in a tool or automation strategy that
12:04 will do this for you thereby you can
12:06 save time and a lot of effort on your part
12:07 part
12:08 and obviously tests that require
12:11 multiple data sets rather than manually
12:13 typing in information into forms or
12:16 fields automate this process to read an
12:17 information from a data source and
12:20 automatically type into the respective
12:22 forms this way you will have better
12:24 handle on your data of variability and
12:26 it also decreases the chances of making
12:29 mistakes repetitively again and suppose
12:30 if you are waiting for an Hans Q in
12:33 response it can be automated so you do
12:34 not have to waste time staring at a
12:36 screen and watching for a response right
12:38 you have other better things to do put
12:40 that time to better use and use
12:42 automated controls like wait until in
12:44 your program code then you have
12:46 non-functional testing a good example of
12:48 automating non functional testing types
12:51 is automating load testing think about
12:53 having to see if your application can
12:56 handle a load of 10,000 users automate
12:58 this testing so you do not have to worry
13:00 about manually spinning up 10,000 users
13:02 hitting your application all at once
13:04 test the Tron on several different
13:06 hardware or software platforms and
13:08 configurations so as the number of
13:10 device users in track width increases
13:13 automating your setup or tearing down
13:15 your setup environment will continue to
13:17 be critical additionally these are
13:19 scripts that you will use over and over
13:19 again in my
13:22 testing frameworks right it's better to
13:24 automate than to do them manually so
13:26 basically the cases where you have to
13:28 automate is when you have repetitive and
13:30 boring tasks or if you have to capture
13:33 some results and share the results or if
13:34 you have to repetitively enter the data
13:37 tasks as in data entry tasks or some
13:39 sort of timing or screening
13:41 responsiveness and especially in load
13:43 testing and suppose if you want to set
13:46 up or tail down your environment set up
13:48 then you can use automation so guys it's
13:50 always better to know when to use event
13:53 to apply automation and software testing
13:55 so guys success and test automation
13:57 process requires careful planning and
13:59 design work start out by creating an
14:01 automated plan this allows you to
14:04 identify the initial set of tests which
14:06 to automate and serve as a guide for
14:08 future testers but there are a lot of
14:09 helpful tools to write automation
14:11 scripts before using those tools it's
14:14 better to identify the process which can
14:15 be used to automate the testing or the
14:17 procedure that you have to follow to
14:19 start automation so as next part of
14:21 session we'll discuss the steps that you
14:22 need to follow when you're performing
14:25 automation testing so like I said all
14:27 your success in test automation requires
14:30 careful planning and design work so
14:32 start out by creating an automation plan
14:35 first of all you should define your goal
14:37 for automated testing and determine
14:39 which type of test you automate once
14:41 you're sure of what kind of test are you
14:43 performing you need to select the tool
14:45 so the first step here is test tool
14:48 selection there are several kinds of
14:50 testing tools available however choosing
14:52 the light tool keeping in mind the
14:54 nature of test involved is very
14:56 important for your automation to be
14:58 successful so whether it's a code driven
15:00 testing process or graphical user
15:02 interface based testing you must sell
15:04 appropriate tool to automate the testing
15:07 so the first step is selecting the
15:09 proper tool required for automation of
15:12 your application or testing next comes
15:14 defining scope of automation as in you
15:17 need to select which test case is taught
15:19 to me here you can follow certain
15:21 pointers like the features that are
15:23 important for business scenarios which
15:26 have large amount of data or those which
15:27 has common functionalities across
15:29 different platforms and applications
15:32 technical feasibility the extent to
15:34 which business components are be used
15:37 the complexity of test cases etc so by
15:39 keeping these pointers in mind you can
15:42 define the scope of automation and the
15:44 third step is planning design and
15:46 development after determining your goal
15:48 and which type of test to automate you
15:50 should decide what actions you automated
15:52 tests will perform planning design and
15:55 development develop test cases don't
15:58 just create test steps that test various
16:00 aspects of applications behavior at one
16:03 time it becomes overwhelming large
16:05 complex automated tests are difficult to
16:07 edit and debug as well so it will be a
16:10 problem for you later on so it is best
16:11 to divide your tests into several
16:14 logical smaller tests so once you've
16:16 developed your test cases or you have
16:17 written your test scripts
16:21 next step is to develop test suits their
16:23 suits are developed to ensure that the
16:24 automated tests which you have written
16:26 run one after the other without any
16:28 manual intervention this is done by
16:30 creating a test suit that has multiple
16:33 test cases a library and command-line
16:36 tool that runs the passu so guys the
16:39 next step is test execution once you're
16:40 done with writing your scripts and
16:43 placing them in suitable test suits the
16:45 next step is to start executing them
16:48 automation scripts are executed during
16:51 this test execution phase so execution
16:53 can be performed using automation tool
16:55 directly or through the test management
16:57 tool which will invoke the automation
16:59 tool which you have chosen to get the
17:01 most out of your automated testing
17:03 testing should be started as early as
17:06 possible and as often as needed as well
17:08 the earlier testers get involved in the
17:10 life cycle of the project the better and
17:12 more you test the mode box you can find
17:16 right so yeah your scripts are executed
17:18 in this phase once executed the next
17:20 step obviously is to create report
17:22 format so that individual test locks
17:24 with details of action performed during
17:26 test are recorded properly for
17:29 references so you define the type of
17:31 test report format to be created
17:34 screenshots messages etc so all such
17:36 things you include in your report as new
17:38 functionalities are added to system
17:40 under test with successive cycles
17:43 automation scripts need to be added
17:45 reviewed and maintained for each release
17:47 cycle right so maintenance becomes
17:49 necessary to improve the effectiveness
17:51 of automation scripts so what I mean
17:54 here is that you do not entirely finish
17:56 a project and start testing suppose if
17:58 you have found some bug you add
18:00 additional features and again start your
18:01 testing from the beginning so a
18:03 maintenance plays a very important role
18:06 and it becomes necessary step to improve
18:07 the effectiveness of your automation
18:09 scripts so you need to follow these
18:11 steps when performing automation testing
18:13 to get the best results and efficient results
18:14 results
18:16 next comes the automation tools there
18:18 are several innovative automation
18:20 testing tools but before we discuss that
18:21 we need to understand there are
18:23 different kind of approaches to
18:25 automation the first one is we have Co
18:27 driven approach this approach uses
18:30 testing frameworks like xunit frameworks
18:32 etcetera the focus here is mainly on
18:35 test gate execution to find out if
18:37 various sections of code are performing
18:39 as per our expectations under different
18:42 conditions or not so Co driven testing
18:44 approach is a popular method used in
18:47 agile software development then we have
18:49 graphical user interface applications
18:51 that have gy s-- or graphical user
18:53 interface may be tested using this
18:55 approach it allows the testers to record
18:58 user actions and analyze them any number
19:00 of times so this is one way of going at
19:03 automation for example if you want to
19:04 test a website you can use automated
19:06 testing tools like selenium that
19:08 provides a record and playback tool for
19:10 authoring tests without any knowledge on
19:12 test scripting language so you do not
19:14 basically have to know the scripting
19:16 language here you do have record and
19:17 playback tool using which you can start
19:19 executing your test test cases can be
19:21 written in any number of programming
19:23 languages like C sharp you have Java a
19:26 Perl Python Ruby and many other options
19:29 so the next approach is using automation
19:31 framework so basically your test
19:32 automation framework is set of
19:34 guidelines which are used to produce
19:37 beneficial results of automation testing
19:39 activity this framework brings together
19:40 function rivalries
19:43 test data sources object details and
19:46 other reusable modules it lays down the
19:48 general rules of automation and it
19:50 simplifies the effort required to bring
19:52 the efficient results and lower your
19:54 maintenance cost as well so basically
19:56 you can say you're setting down a set of
19:58 rules that you need to follow while
19:59 performing your automation
20:01 thing let's consider an example suppose
20:03 if there is any change in a test case
20:06 then only that particular test case file
20:08 needs to be updated without having to
20:10 make any change to the driver or the
20:12 startup script so now if you have
20:14 multiple approaches when it comes to
20:16 frameworks frameworks could be linear
20:18 scripting framework recording and
20:20 replaying test scripts in sequential or
20:22 you can say a linear fashion you have
20:25 data driven framework a constant source
20:27 of test criteria specifies the test
20:29 scripts which you have to run here then
20:31 you have keyboard-driven framework here
20:33 are the tables on a spreadsheet actually
20:35 specify the action of her test tips that
20:37 need to be formed based on the library
20:39 of functions for an assign keyword then
20:41 you have modular testing framework
20:44 modules of an application under test are
20:46 divided and then tested with individual
20:48 test scripts and then they can be
20:51 combined for larger test scripts then
20:52 you have I Bri testing framework
20:54 obviously it's a combination of
20:56 frameworks to leverage the strengths of
20:58 each of the ones which we discussed
20:59 earlier when you've decided to perform
21:01 automation testing you can opt for any
21:03 of these approaches you can go for code
21:05 driven testing you can also go for
21:07 graphical user interface if you're
21:09 testing graphical user interface then
21:10 you can go for a framework approach and
21:12 you have multiple framework options here
21:14 as well like linear which performs
21:16 testing in a linear fashion then you
21:18 have data driven keyword-driven modular
21:20 testing and hybrid testing which is a
21:22 combination of all the other framework
21:24 types so yoga is basically there are
21:26 ways you can implement automation well
21:28 software testing so now moving on to
21:29 test automation tools
21:32 selecting an automated testing tool is
21:34 essential for test automation well there
21:36 are lot of automated testing tools in
21:39 market and it is important to choose the
21:41 automated testing tool that best suits
21:43 your requirement so basically when
21:45 you're trying to test or select an
21:47 automation tool please do follow the key
21:50 points which I'll mention of first of
21:52 all check if the tool is compatible with
21:53 platforms and the different kind of
21:55 technology that you're using ask
21:57 yourself do you need support for mobile
21:59 automation testing or different other
22:01 kinds of testing are you testing dotnet
22:05 c-sharp or other applications if yes and
22:08 then on what operating systems so next
22:10 flexibility of the testers also plays a
22:12 very important role that is why
22:14 kind of skills your tester have also
22:16 plays a very important role for example
22:18 can your QA Department write automated
22:20 test scripts or is there a need for
22:22 keyword testing thirdly does the
22:25 automated testing tool support record
22:27 and playback test creation as well as
22:29 manual creation of automated tests so
22:30 basically you need to consider these
22:33 sort of questions or situations before
22:35 you go ahead and select a tool you can
22:37 also look if the tool includes features
22:39 for implementing checkpoints to verify
22:42 values databases or key functionality of
22:44 your application you need to create
22:45 automated tests that are reusable
22:47 maintainable resistant to changes in the
22:50 application UI right so ask yourself
22:53 will my automated test break if my UI
22:55 changes so based on that choose a to
22:58 make sure that the application is stable
23:00 enough to automate the early development
23:02 cycle unless or otherwise it is agile
23:04 environment it not be a good idea and
23:07 finally the cost and therefore that you
23:09 need to put in is also a very valuable
23:11 concept that you should consider when
23:13 you're choosing an automation tool for
23:15 your testing well these are certain
23:17 categories or scenarios or key points
23:19 that you should take care of when you're
23:21 actually choosing an automation tool now
23:23 to name few popular automation testing
23:26 tools we have selenium selenium is a
23:28 popular testing framework to perform web
23:30 application testing across multiple
23:32 browsers and platforms like Windows Mac
23:36 Linux then we have water W ATI are
23:38 basically it's pronounced as water is an
23:40 open source testing tool made up of Ruby
23:42 libraries to automate web application
23:44 testing then you have something called
23:47 ranorex it is inflexible all-in-one GUI
23:48 testing tool
23:49 so using Analects you can execute
23:51 automated tests flawlessly throughout
23:53 all environments and browsers and
23:56 devices then you have a PM it's a mobile
23:58 testing tool it is an open source mobile
24:00 test automation software obviously it's
24:02 free and supported by a high active
24:06 community of developers and experts so
24:07 apart from this you also have zypher
24:10 Tasker for end-to-end testing then HPE
24:13 or unified functional testing which was
24:15 formerly known as HP quick test
24:17 professional or qtp and I can just keep
24:19 going there are plenty of automation
24:22 testing tools so tool selection is one
24:24 of the biggest challenges that need to
24:26 be tackled before you actually start
24:28 your automation so first identify the
24:31 requirements explore various tools get
24:33 to know them and their capabilities set
24:35 the expectations from the tooth and go
24:37 for a proof-of-concept so that's how you
24:39 choose a tool of your choice
24:42 so guys in some situations automation
24:44 testing is very important but as much it
24:47 is comfortable that much it is risky too
24:49 so if you decide to do automation
24:50 testing then think of following
24:53 scenarios first starting cause for an
24:56 automation is very high automation tool
24:57 purchasing costs training and
25:00 maintenance of test grip all this costs
25:02 are very high because of this reason
25:04 some companies are worried to take
25:06 decision to automate their work secondly
25:08 automation is not hundred-person
25:11 automation testing cannot be 100% and
25:13 don't think of that there are areas like
25:15 user interface documentation
25:18 installation compatibility and recovery
25:20 where testing should be done manually
25:22 you can't do all this using tools you
25:24 need to have a person involved in this
25:26 and another risk that you might
25:28 encounter is when you have unrealistic
25:30 expectations from the automation testing
25:32 tool so like I said earlier know the
25:34 requirement study different kind of
25:36 tools get to know their capabilities and
25:38 choose the tool and then comes the
25:40 incompatibility of automation testing
25:42 tools with the test environment and
25:44 other software testing tools and test
25:46 environment then you have vendor issues
25:48 like inability to provide technical
25:50 support inability to update the
25:52 automation testing tools with changes in
25:54 software testing platform and all that
25:56 and one more point do not automate
25:59 unfixed user interface be careful before
26:01 automating user interface if user
26:03 interface is changing always costs
26:06 associated with script maintenance will
26:08 be very high so basic user interface
26:10 automation is enough in such cases
26:13 by mentioning all this points what I
26:14 wanted to tell you as automation is not
26:17 possible every time and these are some
26:19 cases where you might have to start
26:20 looking twice before you actually
26:23 implement automation here so guys there
26:25 is no silver bullet for testing during
26:27 the development process despite the wide
26:29 variety of techniques and tools we
26:31 cannot rely on a single approach
26:34 automated and manual testing each have
26:36 this strengths and weaknesses what we
26:38 want to stress here is that no matter
26:40 how great automated tests are you cannot
26:42 automate everything manual tests play
26:44 important role in software development
26:46 as well and they come handy when you
26:49 cannot automate the process so guys we
26:50 have reached the end of the session and
26:53 by now I'm sure you know what automation
26:55 testing is and benefits of using
26:57 automation testing Vento uses and which
27:00 test cases need to be automated and how
27:02 different it is from manual testing so
27:04 make sure to consider all this points
27:06 when you go ahead with automation next
27:08 time so guys we have reached the end of
27:10 the session and I hope you have
27:12 understood what we have discussed here
27:14 and if you have any doubt or queries
27:16 regarding any part of the session please
27:17 to mention in the comment section below
27:19 and we'll get back to you as soon as
27:22 possible thank you guys and we'll meet
27:24 you in the next session I hope you have
27:26 enjoyed listening to this video please
27:28 be kind enough to like it and you can
27:31 comment any of your doubts and queries
27:33 and we will reply them at the earliest
27:36 do look out for more videos in our
27:38 playlist and subscribe to any rekha
