Currently there are few issues users are facing when executing Selenium tests on chrome browser.

If have upgraded your chrome browser recently, you will see below issue -

1. Starting ChromeDriver 111.0.5563.64 (c710e93d5b63b7095afe8c2c17df34408078439d-refs/branch-heads/5563@{#995}) on port 13894
Only local connections are allowed.
Please see https://chromedriver.chromium.org/security-considerations for suggestions on keeping ChromeDriver safe.
ChromeDriver was started successfully.

Selenium's headless mode allows running browser tests without a visible browser window by configuring the browser driver with the headless option. This approach enables faster and more efficient test execution as rendering the browser window is unnecessary.

Earlier to execute your Selenium tests in headless mode, you had to utilize the ChromeOptions as shown below.

ChromeOptions options = new ChromeOptions();
options.setHeadless(true);

By using setHeadless() method, you will accomplish the same result.

Selenium Manager is a new tool that helps to get a working environment to run Selenium without having worried about setting path or adding another extra driver manager plugin. With latest version 4.6, Selenium Manager will configure the required browser drivers for Chrome, Firefox, and Edge if they are not present on the PATH.

In Selenium 4, the parameters received in Waits and Timeout have changed from expecting (long time, TimeUnit unit) to expect (Duration duration) which you see a deprecation message for all our tests.

What are Wait commands in Selenium?

It is projected that in 2020 and forward, challenges in automation testing are growing by leaps. Some of these challenges include picking an appropriate tool, skilled testers, upfront expenses, and time constraints. According to Kumar and Mishra (2016), 30% of QA teams’ effort is utilized in manually writing test cases many times to seek significant returns in the long run. Here it’s very well said that those challenges yield the latest innovative idea - codeless automation testing tools.

Selenium 4 (Alpha) with a new locators called "Relative Locators" earlier it was named "Friendly Locators".

Just to recap, In selenium we have used different types of locators such as ID, Name, CSS Selector, XPath, ClassName, TagName, LinkText and Partial LinkText.

Allure Reporting framework works fine with any test framework like TestNG, JUnit etc. Below example covers the implementation of Allure Reports in Selenium using TestNG, Java and Maven.

Let us first try to understand allure annotations before using them in our selenium example.

@Epic
@Features
@Stories/@Story
@Severity(SeverityLevel.BLOCKER)
@Description("In this cool test we will check cool thing")
@Step
@Attachment
@Link

These annotations are used in the same way like we use TestNG annotations or JUnit annotations.

In order to run our selenium webdriver automation scripts on chrome/firefox browsers, we have to download the binary/.exe files like Chromedriver.exe and geckodriver.exe.

As we know all know that ExtentReport is an HTML reporting library (open source) which can be integrated with Selenium WebDriver.

In this article, we will teach you how to develop advanced extent reports / integrate Extent Reports with your existing test automation framework.

We assume you have a working knowledge on Selenium,TestNG and Maven.

Let us start now !!!!

Importance of Reporting in a Test Automation Framework :-

Until today, we have used below code snippet in our automation scripts to take the screenshot using selenium. But most of them started complaining about FileUtils which was working fine earlier, but is not working after upgrading selenium webdriver with latest version.