How to use getStartTime method of org.openqa.selenium.grid.graphql.Session class

You will have to use below hack to access the local storage in RemoteWebDriver . Tested it on chrome browser using RemoteWebdriver selenium-java - 4.0.0-alpha-2 , Chrome Version 76.0.3809.100 and ChromeDriver 76.0.3809.68 . Working fine for me.

Import below classes

 import org.openqa.selenium.remote.RemoteExecuteMethod;
 import org.openqa.selenium.remote.html5.RemoteWebStorage;
 import org.openqa.selenium.html5.LocalStorage;

Use below code to access the local storage

 RemoteExecuteMethod executeMethod = new RemoteExecuteMethod((RemoteWebDriver) driver);
 RemoteWebStorage webStorage = new RemoteWebStorage(executeMethod);
 LocalStorage storage = webStorage.getLocalStorage();
 storage.setItem("test", "test");

You are using drive.quit() instead of driver.close(). quit closes the driver and window. This is why you get the child error because the driver is no longer available. close(), will close the window but keep the driver alive. I would only use quit at the very end of your program (like a cleanup routine). I ran your code (modified below) on my machine and did not have any errors. Also, you should put this around a try/catch so that you can see what is going on. I found with selenium that the try/catch sometimes shows errors that your console does not show. I had something similar with an earlier project and the try catch assisted with debugging.

package com.kurt.stackoverflow.selenium;
import org.openqa.selenium.WebDriver;
import org.openqa.selenium.firefox.FirefoxDriver;
public class Gecko_Driver
{
    public static void main(String[] args) throws InterruptedException{

    try
    {
       System.setProperty("webdriver.gecko.driver","C:\\tmp\\geckodriver-v0.11.1-win64\\geckodriver.exe");
       WebDriver driver = new FirefoxDriver();
       driver.get("http://www.toolsqa.com");
       Thread.sleep(5000);
       driver.close();
    }
    catch (Exception e)
    {
       System.out.println("Caught message " + e.getMessage());
       driver.close();
    }
}

}

As, when you open a feature file in Eclipse and right-click, then you do not find an option 'Run As->Cucumber Feature', it appears that your Eclipse do not have the required Cucumber Eclipse Plug-in. You can install this plug-in using following steps:

1. Launch Eclipse and navigate to 'Help->Install New Software'.
2. Click on 'Add' button
3. Enter any name e.g. 'Cucumber' and type '' as location.
4. Click on OK.
5. 'Cucumber Eclipse Plugin' option will appear in the available software list.
6. Select the check box against it and click on 'Next' button.
7. Read the terms of license agreement and click on 'I accept the terms of the license agreement” if you agree with the license terms.
8. Click on 'Finish' button.
9. Let it install, it will take few seconds to complete.

After successful installation of this plug-in, if you open any feature file (i.e. file with .feature extension) and right-click, you should see 'Run As->Cucumber Feature' option.

Update 1

In Eclipse, go to 'Windows->Preferences->Run/Debug/Launching/Launch Configuration' and uncheck 'Cucumber Feature' checkbox if it is checked. Refer to below screen shot for more details:

Create a inner class that implements Runnable and call it from a new Thread in com.util.SeleneseTestCase run() method. Something like this:

class YourTestCase extends SeleneseTestCase {
    public class MyRunnable implements Runnable {
        public void run() {
            // Do your have work here
        }
    }

    public void testMethodToExecuteInThread() {
        MyRunnable r = new MyRunnable();
        Thread t = new Thread(r);
        t.start();
    }
}

Update to use outside YourTestCase class

To run an inner class from another class you would need to make it public and then from the outer class execute this:

YourTestCase testCase = new YourTestCase();
YourTestCase.MyRunnable r = testCase.new MyRunnable();

But if you don't need to call it from inside your test case you'd better go with a normal class, make MyRunnable a public class without being in YourTestCase.

Hope it helps.

Finally, here's the solution to this problem.

I added this line to my build.sbt file :

For SBT 0.x:

unmanagedResourceDirectories in Test <+=  baseDirectory ( _ /"target/web/public/test" )

For SBT 1.x:

unmanagedResourceDirectories in Test +=  baseDirectory ( _ /"target/web/public/test" ).value

Thanks to @MarkVedder and @JarmoPertman for their great comments who put me on this solution!

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.

Just specify the path to the binary of the version..may be, like-

FirefoxBinary binary = new FirefoxBinary(new File("path_to_bin"));
FirefoxProfile profile = new FirefoxProfile();
WebDriver driver = new FirefoxDriver(binary, profile);

The problem is, you cannot make selenium send batch getAttribute() calls for multiple elements. Here is a similar problem I've looked into - it is about making isDisplayed() work for multiple elements without making JSON Wire protocol requests for every element in a list:

• How can Selenium batch many isElementDisplayed calls?

But, as opposed to this isDisplayed() problem, here we can execute javascript and reliably get the class attribute values for every element on a page, something like this to get you started:

JavascriptExecutor js = (JavascriptExecutor) driver;
js.executeScript("var result = []; " +
"var all = document.getElementsByTagName('*'); " +
"for (var i=0, max=all.length; i < max; i++) { " +
"    result.push({'tag': all[i].tagName, 'class': all[i].getAttribute('class')}); " +
"} " +
" return result; ");

A few quick searches led me to this:

http://blogs.steeplesoft.com/posts/2012/grabbing-screenshots-of-failed-selenium-tests.html

Basically, he recommends creating a JUnit4 Rule that wraps the test Statement in a try/catch block in which he calls:

imageFileOutputStream.write(
    ((TakesScreenshot) driver).getScreenshotAs(OutputType.BYTES));

Does that work for your problem?