SCENARIOS THAT SHOULD NEVER BE AUTOMATED WITH SELENIUM TWO-FACTOR AUTHENTICATION (2FA): Push messages, OTPs, etc., are generated by applications by using an authenticator and then sending OTP by Email or SMS. Specific user credentials that are used for running automated tests should be disabled by 2FA 2FA should be disabled in the test environment while the tests are still being run 2FA should be disabled when specific IPs is used for logging in.
PERFORMANCE TESTING: Another test scenario is performance testing that cannot be automated with selenium. Real time scenarios can be created by Selenium WebDriver for performance test execution, but, still, it doesn’t yield favourable results.
LINK SPIDERING: Application crawling or link spidering saves cost and time by finding out the broken links. In order to crawl through links, Selenium webdriver is not a recommended tool because to crawl, it takes more than a minute based on how the tests are written.
CAPTCHA: On most websites, a CAPTCHA verification can be seen to verify whether the user is a human or a bot. Automation is prevented by CAPTCHA, otherwise, what it is intended to do will eventually not happen as it will fail to perform. CAPTCHA verification cannot be used by Selenium.
VISUAL TESTING: Screenshot testing or visual automated testing focuses on checking whether the GUI is looking as intended by the end-user. Screenshots of the web elements and the full page can be captured by Selenium. How the page looks needs to be checked on different devices and with different resolutions