While there
are plenty of situations where test automation check out, some test situations
ought to never be automated through the program utilizing a device like
Selenium WebDriver.
The
following are 10 models, alongside my clarification of why automation simply
doesn't seem OK for each situation. I'll likewise give you a substitute
methodology for each.
1. CAPTCHA
CAPTCHA is
another way to say "Totally Automated Public Turing test to differentiate
Computers and Humans." It exists to forestall automation, so it's not even
worth difficult. In any case, it neglects to be CAPTCHA, on the grounds that it
will not have the option to differentiate people and PCs.
Two
essential techniques exist to get around CAPTCHA checks during testing. They
are as per the following:
Impair
CAPTCHAs in your test environment. This could be a straightforward setup in the
product under test. Or on the other hand this could be a URL boundary that the
test sets.
Add a snare
to permit tests to sidestep the CAPTCHA.
2. Visual testing
Visual
automated testing implies checking how a page renders and seems to the end
user. This is very significant to beware of different gadgets and screen goals.
A significant number of us attempt to do this by checking for the presence of
handfuls or even many components on a solitary page with code. WebDriver isn't
the right device for this.
All things
considered, it's smarter to utilize a devoted visual testing instrument. Here
is an illustration of me testing my site on the most famous screen goals:
Visual
testing Ultimateqa.com
What's
more, here is the straightforward code to get this going:
Visual
testing code
3. Two-factor verification
Another
situation that you shouldn't automate through UI is two-factor verification (or
2FA). This is where a one-time secret word is created utilizing
"authenticator" portable applications like Google Authenticator or
Microsoft Authenticator, and sent by SMS or email.
It's a
critical test to automate it in Selenium, however that doesn't mean it isn't
possible. And keeping in mind that you can automate it, it's one more layer to
add and isn't as secure. Accordingly, it's ideal to try not to automate it
through and through.
The three
choices to get around 2FA checks are as per the following:
· Cripple 2FA for specific users in
the test environment, so you can involve those user certifications in the
automation.
· Cripple 2FA in your test
environment.
· Cripple 2FA assuming you sign in
from specific IPs. (This way you can arrange the test machine IPs to keep away
from this.)
4. File downloads
It's not so
great to automate file downloads through UI in light of the fact that the API
doesn't uncover download progress. Downloading files isn't viewed as a
fundamental part of imitating user interaction with the web platform.
Subsequently,
you ought to consider finishing this workaround: Find the connection utilizing
Selenium, alongside any expected cookies, and pass it to a HTTP demand library,
for example, REST Assured (Java), bring (JavaScript), or libcurl
(cross-platform).
5. HTTP response codes
HTTP status
codes are standard response codes given by site servers on the Internet. The
codes assist with recognizing the reason for the issue when a page or other
asset doesn't stack as expected. In automated functional testing, checking the
status code is certainly not an especially significant detail of a test's
disappointment; the means that went before it are more significant.
It's
smarter to keep API testing at this layer. WebDriver isn't an API testing
instrument. Thus, you can utilize libraries, for example, REST Assured (Java),
get (JavaScript), and RestSharp (.NET)
6. Gmail, email, and Facebook logins
Another
situation where you shouldn't automate through UI is Gmail, email, and Facebook
logins. It's not prescribed to utilize WebDriver to sign into these sorts of
locales. It's against the utilization terms, and it's sluggish and
questionable.
Taking
everything into account, longer tests are more delicate and untrustworthy,
which jeopardizes you for the test falling flat. An investigation of north of 2
billion tests affirmed that tests enduring longer than 2 minutes are two times
as prone to fizzle.
All things
considered, it's ideal to utilize the APIs that email suppliers offer or, on
account of Facebook, the engineer devices administration that uncovered an API
for making test accounts. (The Gmail API is here.)
Utilizing
an API could appear to be some extra difficult work, yet you'll be repaid in
speed, unwavering quality, and dependability. The API is likewise far-fetched
to change. Notwithstanding, pages and HTML finders change frequently and expect
you to refresh your test structure.
7. Execution testing
Execution
testing utilizing Selenium and WebDriver is by and large not prompted in light
of the fact that it's not streamlined for the gig and you're probably not going
to come by commendable outcomes. WebDriver tests are exposed to many marks of
outside and inner delicacy that are unchangeable as far as you might be
concerned.
These
incorporate program startup speed, the speed of HTTP servers, the response of
outsider servers that have JavaScript or CSS, and the instrumentation
punishment of the WebDriver execution itself, to give some examples. It will
cause varieties in your outcomes. You will get a more slow presentation test
that incorporates back-end and front-end execution.
All things
being equal, utilize a free device like Google Lighthouse for front-end
execution. Then, play out a different test for burden or stress testing
utilizing a free device like Apache JMeter.
To find
what to improve, you should have the option to examine in general execution
free of environmental contrasts, distinguish unfortunate code practices, and
break down the presentation of individual assets (i.e., CSS or JavaScript).
8. Connect spidering
I don't
prescribe utilizing WebDriver to perform connect spidering — at the end of the
day, to bug through joins. You can make it happen, however WebDriver is
certainly not the ideal apparatus for this undertaking since it needs time to
fire up. That can require as long as a moment, contingent upon how your test is
composed, just to get to the page and cross through the Document Object Model.
Moreover,
composing the rationale of navigating pages and catching connections is
essentially an exercise in futility.
Rather than
utilizing WebDriver, there are a lot less difficult techniques. A fast pursuit
uncovers these two free devices:
www.brokenlinkcheck.com,
which tracked down every one of the wrecked connections on my site right away
www.deadlinkchecker.com
9. Video web based
Video web
based is turning out to be more famous nowadays, however you probably shouldn't
automate it through UI. Generally, Selenium will not have the option to
perceive video controls. JavaScript Executor and flex-ui-selenium will work
somewhat, yet they are not no doubt solid.
All things
considered, look at StreamTest, a free device that can gauge the end user's
nature of involvement. You could in fact add observing.
10. Crash recovery
Recovery
testing is a product testing procedure that confirms programming's capacity to
recuperate from disappointments, for example, programming and equipment
crashes. You should test your application's crash recovery. It is best tested
physically. It isn't so much that you can't test it utilizing Selenium, yet
doing so isn't plausible or gainful.
For dependability
testing, information is accumulated from different transformative phases, like
the plan and working stages. The tests are restricted because of limitations
like expense and time limitations.
Utilize
elective tests for these circumstances
These are
the main 10 situations to know about that you shouldn't automate through UI.
You can allude to them as you're working and attempting to settle on the best
methodology for while you're creating, coding, and testing.
Despite the
fact that there are workarounds at times, it's dependably astute to consider
the justifications for why these specific components ought not be automated in
any case.
However,
learn selenium testing to
know where it could be applied from Technosoft Academy.
