How to use getSessionId method of org.openqa.selenium.remote.Command class

Yes, you can start a selenium gird with multiple node on single machine, but RAM should be at least 8GB because it will running test suites with more than 4 browser instance it need more RAM if not browser gets closed. http://selenium-release.storage.googleapis.com/index.html Download standalone jar.

java -jar selenium-server-standalone-2.45.0.jar -role hub 

It will start hub .

To start nodes open different cmd and type following command to start 'n' number nodes. The command is below:

java -jar lib/selenium-server-standalone-2.43.1.jar -role node  -hub http://localhost:4444/grid/register -port 5555

java -jar lib/selenium-server-standalone-2.43.1.jar -role node  -hub http://localhost:4444/grid/register -port 6666

java -jar lib/selenium-server-standalone-2.43.1.jar -role node  -hub http://localhost:4444/grid/register -port 7777

If you want to run same test case in different browser download the browser drivers here

Run the following command to start different browsers: For example:

java -jar selenium-server-standalone-2.45.0.jar -role webdriver -hub http://localhost:4444/grid/register -Dwebdriver.chrome.driver=C:\Users\xyz\Desktop\chromedriver.exe

java -jar selenium-server-standalone-2.45.0.jar -role webdriver -hub http://localhost:4444/grid/register -port 6666 -Dwebdriver.chrome.driver=C:\Users\xyz\Desktop\chromedriver.exe.

This will start chrome browser and node.

One workaround is to set the runOrder parameter to alphabetical and then rename your tests to have alphabetical order.

<plugin>
   <groupId>org.apache.maven.plugins</groupId>
   <artifactId>maven-surefire-plugin</artifactId>
   <configuration>
      <runOrder>alphabetical</runOrder>
   </configuration>
</plugin>

This isn't recommended, though - unit tests should be independent of each other. The execution order shouldn't matter.

Naif,

Actually, your above question is different than the actual question hence you should have asked it as a separate question. Still, I'm answering to your previous question.

The error is because the element you're trying to click on isn't visible. Before you click on element, it should be visible. You can do this by following -

WebElement element = driver.findElement(By.xpath("//div[2]/div[2]"));
WebDriverWait wait = new WebDriverWait(driver, 20); //here, wait time is 20 seconds

wait.until(ExpectedConditions.visibilityOf(element)); //this will wait for elememt to be visible for 20 seconds
element.click(); //now it clicks on element

If above doesn't work, you can click on element by executing javascript(but this isn't a good practice)

JavascriptExecutor js = (JavascriptExecutor)driver;
js.executeScript("arguments[0].click();", element);

Another answer is not correct. There is also a vulnerability for version 1.x. CVE-2021-4104:

A flaw was found in the Java logging library Apache Log4j in version 1.x. JMSAppender in Log4j 1.x is vulnerable to deserialization of untrusted data. This allows a remote attacker to execute code on the server if the deployed application is configured to use JMSAppender and to the attacker's JMS Broker.

For the mitigation of this vulnerability:

These are the possible mitigations for this flaw for releases version 1.x:

• Comment out or remove JMSAppender in the Log4j configuration if it is used

• Remove the JMSAppender class from the classpath. For example:

  zip -q -d log4j-*.jar org/apache/log4j/net/JMSAppender.class
  

• Restrict access for the OS user on the platform running the application to prevent modifying the Log4j configuration by the attacker.

Your problem is here:

@After
    public void test_Cleaning(){
        System.out.println("Closing Browser");
        baseURL = null;
        driver.close();
        driver.quit();
    }

Try only with close(). Explanation here.

There a couple of things which you have to take care while dealing with InternetExplorer as follows :

As you mentioned There is a known issue with selenium documented in GitHub, these are not issues as such but is the combined set of Required Configuration while dealing with InternetExplorer. Without taking care of these settings InternetExplorer may not behave as per expectation. The following items are critical to demonstrate proper behavior of InternetExplorer v11 :

• Enhanced Protected Mode must be disabled for IE 10 and higher. This option is found in the Advanced tab of the Internet Options dialog.
• The browser Zoom Level must be set to 100% so that the native mouse events can be set to the correct coordinates.
• You have to set Change the size of text, apps, and other items to 100% in display settings.

• For IE 11, you will need to set a registry entry on the target computer so that the driver can maintain a connection to the instance of Internet Explorer it creates.

  For 32-bit Windows installations, the key you have to look in the registry is : 
  HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_BFCACHE
  
  For 64-bit Windows installations, the key is :
  HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_BFCACHE
  
  The FEATURE_BFCACHE subkey may or may not be present, and should be created if it is not present.
  

• Native Events : The advantage of using native events is that it does not rely on the JavaScript sandbox, and it ensures proper JavaScript event propagation within the browser. However, there are currently some issues with mouse events when the IE browser window does not have focus, and when attempting to hover over elements.

• Browser Focus : IE itself appears to not fully respect the Windows messages we send the IE browser window (WM_MOUSEDOWN and WM_MOUSEUP) if the window doesn't have the focus.

• You can find a detailed discussion on Native Events and Browser Focus here.

• Now, you have to configure all these parameters through DesiredCapabilities Class as follows :

  DesiredCapabilities cap = DesiredCapabilities.internetExplorer();
  cap.setCapability("ignoreProtectedModeSettings",1);
  cap.setCapability("IntroduceInstabilityByIgnoringProtectedModeSettings",true);
  cap.setCapability("nativeEvents",true);
  cap.setCapability("browserFocus",true);
  cap.setCapability("ignoreZoomSetting", true);
  cap.setCapability("requireWindowFocus","true");
  cap.setCapability("INTRODUCE_FLAKINESS_BY_IGNORING_SECURITY_DOMAINS", true);
  

• As per Best Programming practices Thread.sleep(1000); is a huge No as it degrades the Test Performance

• Now, as you are aware that the Browser Clients lags the WebDriver instance so we have to often sync up them. So before you collect the windowHandles you have to induce WebDriverWait as follows for which you can find a detailed discussion here :

  WebElement popup= driver.findElement(By.name("popup"));
  popup.click();
  new WebDriverWait(driver,5).until(ExpectedConditions.numberOfWindowsToBe(2));
  Set<String> windowHandles = driver.getWindowHandles();      
  System.out.println(windowHandles);
  

Update

I can see from your comments :

"Enable Enhanced Protected Mode" is unchecked in IE options. – Renjith Jan 9 at 7:26

Here is the exert from @JimEvans sensetional blog on Protected Mode settings and the Capabilities hack where @JimEvans nails the context in a clear and unambiguous term :

When the rewritten IE driver was first introduced, it was decided that it would enforce its required Protected Mode settings, and throw an exception if they were not properly set. Protected Mode settings, like almost all other settings of IE, are stored in the Windows registry, and are checked when the browser is instantiated. However, some misguided IT departments make it impossible for developers and testers to set even the most basic settings on their machines.

The driver needed a workaround for people who couldn't set those IE settings because their machine was overly locked down. That's what the capability setting is intended to be used for. It simply bypasses the registry check. Using the capability doesn't solve the underlying problem though. If a Protected Mode boundary is crossed, very unexpected behavior including hangs, element location not working, and clicks not being propagated, could result. To help warn people of this potential problem, the capability was given big scary-sounding names like INTRODUCE_FLAKINESS_BY_IGNORING_SECURITY_DOMAINS in Java and IntroduceInstabilityByIgnoringProtectedModeSettings in .NET. We really thought that telling the user that using this setting would introduce potential badness in their code would discourage its use, but it turned out not to be so.

If you are able to set the Protected Mode settings of IE, and you are still using the capability you are risking the stability of your code. Don't do it. Set the settings. It's not that hard.

Here is how you need to set the Protected Mode settings :

• Here is another discussion on Selenium IEServerDriver not finding new windows for IE9 where the solution was Turning on Compatibility Mode

I was seeing the same issue. The problem only appears when using Chrome 65 (currently: dev channel). With Chrome 64 (both stable channel and beta channel) everything worked fine.

It turns out I had an old chromedriver installed. Specifically, I was using chrome=65.0.3325.51 with chromedriver=2.29.461585. Running npm install -g chromedriver bumped chromedriver to 2.35.528157 and now the problem is solved.

TL;DR: run npm install -g chromedriver

One of the differences between Katalon and groovy is that groovy is lightweight as compared to Katalon. Since Katalon offers variety of features in a container, it is easier to use. Scripting is very much encapsulated within it. Groovy on other had provides many features for testing - Do check out Spock (http://spockframework.org) which is mainly used for testing Java/Groovy applications.

In a nut shell; which should be chosen really depends on the team composition of programmers, tech stack on which your app is built, maintainability of the application in scope. Hope it helps...

See e.g. this Github issue, some dependencies can drag in an outdated version of xml-apis which can cause this, a solution that worked for me was to add a specific dependency on xml-apis, e.g. with Maven something like

<dependency>
    <groupId>xml-apis</groupId>
    <artifactId>xml-apis</artifactId>
    <version>1.4.01</version>
</dependency>