Selenium mesh V.S. Jenkins

Question

I am using TestNG environment for selenium webdriver scripts. I run them periodically using Jenkins in slave machines. I do not use selenium mesh. What is the advantage of using selenium mesh over jenkins when working with webdriver automated test stands? Please clarify whether my understanding is completely wrong.

Answer 1

Well Selenium Grid helps you run your tests in parallel on several different nodes (slaves) that need to be registered in a central hub. You create your driver object by sending a request to the hub, which finds the corresponding node based on the desired feature that you installed and performs a test on that node.

While Jenkins is a continuous integration tool. It cannot distribute your test cases across multiple nodes. In fact, Jenkins is no different from selenium; it's just a CI tool. This is the trigger point of your tests after your builds.

If you need to distribute your tests on different machines, I think you should use Selenium Grid simply because it will manage the distribution and do a lot of work under it.

, jenkins , , , , . Selenium .

Answer 2

( Selenium Plugin) Selenium. Jenkins ( ).

Selenium Grid Selenium Jenkins, .

Jenkins Selenium Plugin ?

• Selenium node
• Jenkins (, node )

Grid Jenkins:

• .
• (Jenkins, , )
• (CPU, Memory Network I/O) Jenkins .

Jenkins, , - , Grid node Jenkins. , "" , (, , Jenkins.)

- , Selenium. Selenium Grid, - , - (, ).

Answer 3

Selenium Grid . / .

What always helped me was to think of a manager with a clip as a grid. Top-level management (Jenkins) tells the manager (Grid) to run these test steps. The manager (Grid) allocates work to employees to actually do this. everything returns to the manager and eventually returns to the top level.