25 Scenarios should not be automated using Selenium WebDriver - By Naveen AutomationLabs

this is naveen here welcome back to naveen automation labs so today i have come up with a new interesting topic that is that these are 25 points that i have written that which should not be automated and we should avoid to automate and some points cannot be automated so that's where the topic name is scenario should and cannot be automated using selenium i'm talking specific to selenium so let's talk about it these are the three uh columns that i have created and the first column first we will talk about that capturings we should not automate capture some people say that can we automate capture or not move there are some certain tools are available some ocr tools are available like optimal card reader or optical image readers are available we can do that but we should avoid because capture are so dynamic in nature and then uh we should uh we cannot redefine that okay yeah this is the exact word or there are different types of captures are available maybe some captures you can see you're looking identify a number of cars identified number of trees over there like that so such kind of things we should not automate if you really want to avoid that in the lower environment you can disable capture and then in the lower environment or the testing environment you can avoid capture and then you can automate those kind of scenarios but we should not try to automate captcha unnecessary second thing is that barcode and the qr code barcode and qr code also selenium does not provide any such apis to automate barcode and the qr code but there are certain third party libraries are available i'm not saying that okay we cannot automate but we should avoid to automate such scenarios which are very very dynamic in nature and then and not reliable at all so we should not automate otp a lot of people say that organizing can be automated otp we can do that we have certain libraries like i have already prepared one video at willow api or such apis are available where we can read the data from the mobile phone or sms or maybe the email id we can do that but if dealer is not working for you let's see for indian number it doesn't work in that case we should not do that and selenium does not provide any api to fetch the data from your sms or something or maybe you can use some certain other third-party libraries or maybe you can use apm to go to the sms or message app over there and fetch the data but this is not at all the level so we should try to avoid otp scenarios two-factor authentication this is totally based out of apis and authentication is happening over there by calling the third-party authentication or maybe internal authentication or maybe some authorization is getting called it has to be verified with your two factors one factor is your email id or maybe second factor is your mobile phone or something like this so in that case we should not automate success with selenium audio video clips and streaming not at all eligible it's not at all good idea that you are going to automate some video streaming or video clips let's see youtube videos or something like this those are not at all reliable and we should not do automate such things unnecessary six point windows and desktop application that's a limitation with the selenium we cannot automate let's see for skype let's see for uh zoom i cannot automate those things i cannot automate file upload using selenium like that and there are different types of file upload and different type of windows based applications are available there are certain third party libraries like we have robot libraries or maybe we can use uh auto id or coli we can do that but with selenium we cannot automate that that's a limitation of a silly name and we should actually avoid to automate and we should not try to automate such things because what will happen today you are automating or handling these sort of scenarios let's see with auto id but it won't work on the docker containers it won't work on the on jenkins machine or linux machine it's only working with the windows machine in that case so it would work if you're using security there are multiple type of different types of resolutions are there and different types of screen size are available you have to keep taking the storage for a different type of resolutions and the screen size for each and every button and the link and the web element and then you have to do a lot of maintenance if you're using sequel for that so that's why i would recommend to use uh selenium and automation for such values as well then for example like hardware testing credit card swap we used to have such kind of scenarios to previous company where we used to do some respiratory devices and then uh normal physical devices we were using over there and till till this particular point we were doing automation but when we come over here then we stop automation and we were doing it manually for those order ids and the payment ids facebook gmail and twitter linkedin such applications guys we should not try to automate i always say that guys please do not practice on such applications like facebook twitter these applications they will restrict the automation after a couple of hits and that's a totally violation of their policy also that we should not hit unnecessary these applications because if you're hitting their facebook application or it's a gmail application and i'm trying to automate inbox and send feature or send mail feature or compose mail feature after a couple of hits gmail will block your request automatically better to use gmail apis or facebook apis you can use a twitter api or the linkedin developer apis you can do that and you should do the backend automation or ap automation for these applications but you should not automate it from the ui nine point flash objects flag silver light application those objects cannot be recognized by from the selenium so better to avoid unnecessary flash objects and flex applications or silver light delphi objects are available we really don't need to automate such things with respect to selenium so we should avoid that yeah performance testing selenium is not responsible for the performance testing guys selenium is a tool which automates the browser selenium does not provide any apis or any library to generate the multi-threading concept or load testing or a stress testing or generate virtual users or something like this we should not do and we cannot do automation or performance testing sorry we cannot do with selenium virtual keyboard sometimes you see that okay there are certain scenarios that the virtual keyboard a virtual uh keyboard screen will be displayed on the ui that we cannot automate that so it just came into my mind and i thought of writing over there mobile native applications that i cannot automate a specific mobile native application i can automate browser-based application i can automate mobile browsers but i cannot automate mobile native application for that you have to use apm or maybe some other mobile automation tool for that but with selenium i cannot automate that link spiders and link validators sometimes we see that okay let's see on amazon.com we really want to see that okay these are the links are working or not but amazon application let's say having 500 pages i cannot go to each and every page using selenium by using clicking on each and every link and then navigating over there and then checking the url and hitting the api and then checking what is the response code it's a broken link or not for a specific page i can do that but there are certain better tools are available in the market like link validators are available a lot of open source are available in the market you can use link validator testing with those tools instead of selenium so you can avoid these kind of scenarios also http aba testing obviously selenium is not for back-end testing i cannot perform any rest api automation or any kind of api automation for that so we should avoid api testing with that and we can have a rest assured we can combine with selenium and we can use rest assured http line jersey client postmen such kind of libraries we can use that to automate api but selenium cannot automate apa automation which we're testing visual testing means some graphs are available some uh we can do that i'm not saying we cannot do visual testing with any we can do that but it's not that reliable so we should avoid to do video testing for different resolutions for the different uh screen sizes so we should not try to automate unnecessary things with the respect to which we're testing over there then we have large file downloads let's see there is a 1gb file because we don't have any api provided by selenium that okay yes that i'm going to download this particular file it's taking around 10 minutes or 15 minutes then i have to wait for that so selenium does not provide any downloading api that okay yeah this is what the status bar is going on so we don't have such api to check the status that okay how much percentage of the downloaded uh downloading of the file is done or not so i think we should avoid such things in fact it's not that user-based scenario also once we download obviously it will be downloaded it depends on your internet and that's it so it's not applicable for automation also that's why i always say that okay guys 100 automation is a myth we should not try to automate 100 things there are certain things which has to be tested manually you have to go to the application you have to check it over there manually do not try to automate everything and please try to explain the same thing to your manager and do the management also that yeah these are not good candidates for automation we should not do that because these are similar certain limitations are available uh they are not reliable also and take a lot of efforts but uh after a few months you never know that okay you are getting the right results or not so the roi is not that great the return of investment is not that okay so the last point i mean the last column is non-web-based application any kind of non-web-based elements on either it is available on the browser or maybe available on on your desktop on your operating system either it would be a linux machine or mac machine or windows machine your file system over there i cannot automate because those are not web-based applications or those are not web-based elements so selenium can not do that so guys trying to understand that today we are just going to talk about around selenium these are the points that should not be automated and cannot be automated with selenium maybe there are certain tools are available in the market i'm not denying for that definitely there are tools are available but for selenium these are the i would say i don't say limitation but selenium doesn't work in that way so we should not automate certain scenarios and cannot be automated with respect to these scenarios now maps and canvas very very complex uh html file canvas and maps are available as a google map i cannot automate such things and then we should not do that maybe we can hit some javascript interceptor or something like this we can do that but those are not that much reliable so we should avoid a maps and canvas also devices and hardware testing some raspberry devices are there or maybe iot testing that you really want to do that i cannot do this let's see some embedded testing i won't do that some hardware machines are there and that's you're sending some event to the hardware machine some bluetooth machine i cannot automate those things because i'm coming from the rental car background my previous company was into mobility services and then uh we were doing certain kind of testing over there but we were using some different tools over there we were using some python or something like this but it cannot be automated with selenium exfoliating testing guys very important you have to understand that expedited testing we can do automation for that but i think personally and from my point of view we should not automate we should not try to do that because expertly testing that for the user point of view we have to keep checking what kind of application behavior with the different set of data with different set of use cases positive negative testing and we have to keep uh doing those testing we have to keep exploring about the application uh different pages different behavior on the basis of different test data different inputs so i think we should uh avoid expedited testing using selenium because there is no limit for exploited testing and manual testing i think the best one to perform expedited testing and you can automate some very certain important business use cases with respect to exploratory testing in selenium but i think we should avoid exploratory testing using selenium security testing obviously guys selenium does not provide any any api for security testing like sql injection or maybe a cross reference testing or any kind of security injection javascript testing that nearly do that with respect to security any kind of authentication hacking such kind of things we cannot do that with security so we should avoid that usability testing again what kind of user behavior how exactly customer will think about that particular use case or that particular application so it depends on the customer data that how exactly the user is using that particular uh tool using that particular device either it's on android ios chrome browser firefox driver on which uh system the requests are coming when exactly the user base is available so those kind of things we cannot automate and then it's really difficult to manage also so we should avoid uh with respect to selenium for usability also look and feel right that is again again an important thing some people they try to check what is the color what is the look and feel the alignment each and every uh css property we should avoid that because it's just very very dynamic changes dynamic application this is the last point also you can see it over here both the things we should not do that the way the application is so so dynamic every minute the behavior of the application and the objects are getting changed so i think we should avoid to automate with respect to selenium or in fact with respect to any automation tool also the command line interfaces like some command line uh prongs are available and interfaces are available such things we cannot automate with selenium and then we should avoid obviously that for doing automation also such things so these are the 25 points along with again i would say 100 automation is a myth guys we cannot do 100 automation and then you have to understand one thing that automation is not about everything with respect to testing we have to understand that okay along with the manual testing you have to do certain amount of automation automation is helping you at a time of regression it's making your life easy that okay yeah this 30 40 50 things we have automated and then so that we can concentrate on the manual testing at a time of recreation we can concentrate on the important things and the rest of the regulation cycle is done by automation these test cases are getting executed by automation so that i don't mean to waste my time or spend more time on these things or these regression test cases manually because i've already automated that for very good example like cross browser testing and user uh and the user base access control testing and then typical form control features are available navigation features are available typical a feature from on e-commerce application i can automate that so these are the really good candidates for automation and then only we should automate that but these are the important 25 points with respect to selenium guys so if you have any other points in your mind please put in the comment section definitely we will try to add those things as well so yeah thank you so much thanks for watching the video automation labs that's all for today i hope you like this particular video if you like it please subscribe to the channel press the bell icon to get the notification for the next video and take care and see the next video please thank you so much bye

Channel: Naveen AutomationLabs

Views: 28,924

Keywords: selenium webdriver, selenium with OTP, selenium with Gmail automation, selenium bar code, naveen automation labs

Id: sbswAkXXOFY

Length: 15min 42sec (942 seconds)

Published: Tue Dec 01 2020