If there is no DOM associated with the element that you want to interact with(similar to the one in your case), use Java robot class to send a {ENTER}. I believe this will solve your problem.

You'll want to use the various different selenium drivers that can be used to run against different browsers. You'll need either the browser or a similar 'browser driver' program, e.g. chromedriver which can be called. Different browsers can also have different UI and timing issues so you'll need to discover if there are any of them in your app. You'll want to look into using the cloud and setting up connection to remote servers and services such as browserstack and sauce labs. Estimated time to implement: 1-3 months. You should spend time getting it right. Your automated pipeline is key to success.

You can move to debugging your script in following way:

Step 1 : Create the script as per your business requirement. Here i have created one sample test plan for the reference where i have setup all required things as mentioned in snap :

Step 2: If debug plugin has successfully installed then it will appear in the strip right below the menu bar, click on it

It will open new debug window where you will see the debug options as shown in the below snap :

Step 3 : Now select the Test Plan and click on the Start button, It will start debugging your script

Test plan component will display highlighted which is currently being executing , to move the next step click on Step Over Button, Here you can analyze your script the flow and variables, logs and so many things as options are there.

EDIT:

Note: Jmeter 3.0 and 3.1 supports blazemeter step by step debugger plugin version 3.0. blazemeter step by step debugger plugin version 4.0 supported by Jmeter 3.2

This sounds like two different issues. 1. Sometimes you get a NoSuchElementException. 2. Sometimes selenium clicks the wrong element.

I'll focus on the 1st issue as the 2nd issue would probably need more debugging information.

You have a problem with this line:

webDriverWait.Until(ExpectedConditions.ElementTo‌BeClickable(excelSession.FindElementByName("Maximize"))).Click();

First, excelSession.FindElementByName(...) will be called, the result of that will be passed to the ElementToBeClickable method, and that result is passed to Until which will run that action until it returns true. This is a problem because excelSession.FindElementByName throws an exception if the element doesn't exist, so the result can't ever be passed to ElementToBeClickable.

The easiest solution is to pass a By to this method, as that version of ElementToBeClickable will wait until the By successfully finds the element. Or to be more accurate, it will return false if the element doesn't exist.

By maximizeBy = By.Name("Maximize"); 
webDriverWait.Until(
    ExpectedConditions.ElementToBeClickable(‌​excelSession.FindEle‌​ment(maximizeBy)).Cl‌​ick();

That should take care of your issue with it sometimes not clicking the maximize button due to a NoSuchElementException.

Another thing that is likely causing you a lot of grief, is you're eating way too many Exceptions, and then hiding the real exception by trying to guess why an exception was being thrown, and logging that. Generally speaking, try to avoid using Exceptions as logical paths. If an exception gets thrown, feel free to catch a specific Exception (something like NoSuchElementException, not Exception), do some logging or any cleanup that needs to happen, but still throw or attach the original exception message to your exception. Otherwise your going to run into confusing debugging problems.

Best of luck!

No, each "product" has their on version numbers. So each plugin/package being separate from the standard IDE means it has a different number scheme. You need to check the release notes for the plugin/package and check compatibility with Eclipse versions to see which versions are supported with the plugin/package.

This answer doesn't directly get it with the load testing tools, but an alternate method.

Utilize logging to pull logs from each server and set the destination for the logging to an external location. This will allow you to get the logs from each server respectively into a desired location for each server on your systems. You will then be able to compare the server logs with the test execution to be sure know which server was doing what at what time.

Note: You will also need to be sure that the server and application logging is setup to sufficiently capture the traffic/activities you are after.

I am new to mobile app testing. I am trying to understand how appium works. Basically i need to run tests parallel in both android and ios. But the scripts are written in C#. How would this be possible? Does appium work like Selenium Grid?

I am finding an automation testing tool to test a non-GUI installer which is written in Ruby or power script. The automation tool should work on both windows and Mac machines.

I'm trying to set up robot on top of an Eclipse Maven-Selenium-TestNG java project I created, but it doesn't seem to be picking up default keywords (I haven't even tried adding my own yet). I have python 3.4.3 installed on my Win 10 machine and am using the embedded maven that comes with Eclipse.

I started by creating a maven project and adding to pom.xml the dependencies for selenium 3.4, testNG 6.8 and robot 3.0.2, then also added robot plugin 1.4.7. Finally, updated the project so maven downloads all the needed stuff so I don't have to install anything externally.

To test selenium (without robot) I created a textNG class in src>test>java, added a system property pointing to the chromedriver.exe file in my system and added a simple test that opens the browser and navigates to google. It worked, so now I want to add robot framework.

This is my pom.xml file:

<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
  <modelVersion>4.0.0</modelVersion>
  <groupId>com.demo.automation</groupId>
  <artifactId>automated_tests</artifactId>
  <version>0.0.1-SNAPSHOT</version>
  <dependencies>
    <dependency>
      <groupId>org.seleniumhq.selenium</groupId>
      <artifactId>selenium-java</artifactId>
      <version>3.4.0</version>
    </dependency>
    <dependency>
      <groupId>org.testng</groupId>
      <artifactId>testng</artifactId>
      <version>6.8</version>
      <scope>test</scope>
    </dependency>
    <dependency>
        <groupId>org.robotframework</groupId>
        <artifactId>robotframework</artifactId>
        <version>3.0.2</version>
    </dependency>
  </dependencies>
  <build>
    <plugins>
      <plugin>
        <groupId>org.robotframework</groupId>
        <artifactId>robotframework-maven-plugin</artifactId>
        <version>1.4.7</version>
        <executions>
          <execution>
            <goals>
              <goal>run</goal>
            </goals>
          </execution>
        </executions>
      </plugin>
    </plugins>
  </build>  
</project>

I created a file in src/test/robotframework/acceptance, with the following contents (although I've read somewhere that after selenium 2 the "start/stop selenium server" keywords are not necessary, but nothing changes if I remove them):

*** Settings ***
Test Set Up  Start Selenium Server
Test Tear Down  Stop Selenium Server

*** Test Cases ***
Visit google
  Open Browser  https://www.google.com  chrome
  Close Browser

When I run as maven install, I get:

Setup failed: No keyword with name 'Start Selenium Server' found.

Also teardown failed: No keyword with name 'Stop Selenium Server' found.

So why is it that robot is not finding the keywords implementation? And how do I add implementations of my own keywords?

I wanted to check out the headless version but I am still on version 58 even after updating my system

This could dramatically reduce our test suite run time!