multithreading - Selenium tests doesn't work when run in Jmeter with Java Sampler and multiple threads -

I am running a Selenium test for a web site using the Jmater and Java samplers. I've exported the test class, which uses the "Exports from Export -> Export from Export" extension, extends the Java Java Client Client and copies it into Jmter / Lib / Ext. I am using classes from another Java project in my test. I packed this project for .jar and copied it in jmeter / lib. When I run my trial in a thread in Jumetter it works fine, but if I run 2 or more threads, the Selenium web driver fails to find the elements but I think they are visible. I'm new to this, but it seems that Selenium can not work in many threads. What am I doing wrong? help please. According to the guide some restrictions apply to Jmeter's JUnit sample,

The "only time elapsed" juneet request has been entered for sample. You will not be able to see latency or byte matrix because Jmator does not know anything about your Junket Test. Therefore, Jmater is only capable of measuring your test method execution time

There is currently no way to run the JUnit suite or stability according to JM (2.11). Only individual test cases can be performed and only one test case according to the JUnit request sampling example

There are some limitations for JUnit testing designs JMant's multi-pronged nature Due to this, the test developer needs to use a thread-safe approach (i.e. to avoid static fields and methods wherever possible, and keep in mind that the resource is second Thread can be busy)

The limited JUnit request sampling configuration capabilities believe that all pre- and post-test logic should go in ways to set up and tear. If you need to use external data to access Sampler properties files or system properties, then

You are likely to suffer from point 3.

Also, according to

: This project does not intend to change the HTP sample included in JMT. Instead, the end user means measuring the load time and congratulating them.

In addition, from the same source:

By experience, the number of browsers (threads) that the reader makes should be limited by the following formula:

  c = b + 1  

where C = the number of core of the host running the test and N = the number of browsers (Threads) For example, if the current reader host has 4 cores, the formula will generate:

  4 = 3 + 1  

< Blockquote>

meaning 3 in the script Threads must be of MAXIMUM .

So I suggest using Jmator to produce the main load and either in our separate code JUnit Sampler to measure the real-life user experience in a different thread group

in 1 thread