blocks|key|281037|text|Selenium's+website上的文档说明远程控制由以下部分组成|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|281038|281039|a+server|unordered-list-item|style|BOLD|281040|client+libraries|281041|281042|服务器负责执行实际工作(在浏览器中执行操作)，而您的操作规范(+of+execution)来自不同的库。|281043|这称为远程控制，因为服务器不必部署在执行实际脚本的同一台计算机上。这些脚本可以通过网络连接到远程selenium服务器并执行操作。|281044|总而言之，当您使用Selenium+Remote+Control时，您就是在使用服务器%2B客户端库。它们应该一起使用。|281045|我不知道Selenium+2是否也会如此，或者它们是否正在改变一些东西。我只确信Selenium+1就是这样工作的。|281046|entityMap|0|LINK|mutability|MUTABLE|url|http://seleniumhq.org/projects/remote-control/^0|0|I|0|0|0|0|8|0|0|G|0|0|0|3|5|6|1B|4|0|0|0|0^^$0|@$1|2|3|4|5|6|7|12|8|@]|9|@$A|13|B|14|1|15]]|C|$]]|$1|D|3|-4|5|6|7|16|8|@]|9|@]|C|$]]|$1|E|3|F|5|G|7|17|8|@$A|18|B|19|H|I]]|9|@]|C|$]]|$1|J|3|K|5|G|7|1A|8|@$A|1B|B|1C|H|I]]|9|@]|C|$]]|$1|L|3|-4|5|6|7|1D|8|@]|9|@]|C|$]]|$1|M|3|N|5|6|7|1E|8|@$A|1F|B|1G|H|I]|$A|1H|B|1I|H|I]|$A|1J|B|1K|H|I]]|9|@]|C|$]]|$1|O|3|P|5|6|7|1L|8|@]|9|@]|C|$]]|$1|Q|3|R|5|6|7|1M|8|@]|9|@]|C|$]]|$1|S|3|T|5|6|7|1N|8|@]|9|@]|C|$]]|$1|U|3|-4|5|6|7|1O|8|@]|9|@]|C|$]]]|V|$W|$5|X|Y|Z|C|$10|11]]]]

The documentation on <a href="http://seleniumhq.org/projects/remote-control/" rel="noreferrer">Selenium's website</a> says that the Remote Control consist of 

<ul>
<li>a server</li>
<li>client libraries</li>
</ul>

The server is responsible for doing the actual work (executing actions in the browser) while your specifications for actions (the control of execution) comes from the different libraries. 

This is called the Remote Control because the server does not have to be deployed on the same machine where the actual scripts are executed. The scripts can connect to a remote selenium server over the network and execute actions. 

To sum up, when you are using the Selenium Remote Control, you are using the server + client libraries. They are meant to be used together. 

I do not know if this is going to be the same for Selenium 2 or if they are changing things. I am only confident this is how things work for Selenium 1.

blocks|key|2995853|text|你应该看看documentation+outlining+the+different+parts+of+Selenium。这是一个很好的起点，因为它将引导您完成安装过程。完全公开，我帮你写文档。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2995854|至于这些下载，您拥有的第一个链接是该项目的官方版本。第二个链接是当前的beta版本，一旦他们达到2.0版本，他们就会出现在网站上。|2995855|2995856|Selenium核心-更像是selenium的一个组件，而不是一个独立的项目。不深入项目历史，Selenium曾经只是一个自动化浏览器的.js文件的集合。没有人直接使用它们，它们只是用于遗留的firefox+-一个用于记录/回放的reasons.|unordered-list-item|style|BOLD|2995857|Selenium插件。您可能想从这个开始，以适应该应用程序接口，但您将使用soon|2995858|Selenium+RC，当您确实使用它时，您将使用Selenium+Remote+Control。Selenium+1.x是一个客户端-服务器架构。您可以使用RC库来编写与服务器通信的测试程序，然后服务器将这些命令转发给浏览器。|2995859|Selenium网格-一种在分布式计算机网络上运行Selenium测试的方法。一旦您有了大量的eclipse测试--一个利用selenium进行测试的基于eclipse的工具，那么这对于加快速度是非常有用的。不确定它有多流行is.|2995860|Bromine+-一个基于web的脚本和测试管理工具。使用selenium+RC运行测试。|2995861|2995862|然后我们进入Selenium+2测试版。Selenium+2与Selenium+1模型有很大不同，因为它不需要Selenium服务器。我之所以说“需要”，是因为在另一台计算机上远程运行测试是可选的。Selenium+Server+Standalone是用于此目的的服务器。它兼容Selenium-RC以及用于远程目的的Selenium+2。|2995863|您可能已经看到Selenium+2被称为WebDriver。WebDriver是几年前合并的另一个项目，成为Selenium+2的基础。这就是Selenium+2具有WebDriver接口的原因，有时称为"WebDriver“api，以区别于Selenium-RC。|2995864|如果你刚刚开始，我会看看Selenium+2，它现在得到了99.9%25的开发人员的喜爱，Selenium+1.xAPI不会再进一步发展了。截至2011年1月，Java库是最受支持的，紧随其后的是.Net和Python/Ruby。Watir+(流行的Ruby浏览器自动化库)在幕后使用selenium，如果您想要另一个api选择的话。|2995865|entityMap|0|LINK|mutability|MUTABLE|url|http://seleniumhq.org/docs/02_selenium_basics.html#getting-started-choosing-your-selenium-tool^0|5|1J|0|0|0|0|0|A|0|0|15|0|0|36|0|0|1K|0|0|7|0|0|6|D|0|0|0^^$0|@$1|2|3|4|5|6|7|18|8|@]|9|@$A|19|B|1A|1|1B]]|C|$]]|$1|D|3|E|5|6|7|1C|8|@]|9|@]|C|$]]|$1|F|3|-4|5|6|7|1D|8|@]|9|@]|C|$]]|$1|G|3|H|5|I|7|1E|8|@$A|1F|B|1G|J|K]]|9|@]|C|$]]|$1|L|3|M|5|I|7|1H|8|@$A|1I|B|1J|J|K]]|9|@]|C|$]]|$1|N|3|O|5|I|7|1K|8|@$A|1L|B|1M|J|K]]|9|@]|C|$]]|$1|P|3|Q|5|I|7|1N|8|@$A|1O|B|1P|J|K]]|9|@]|C|$]]|$1|R|3|S|5|I|7|1Q|8|@$A|1R|B|1S|J|K]]|9|@]|C|$]]|$1|T|3|-4|5|6|7|1T|8|@]|9|@]|C|$]]|$1|U|3|V|5|6|7|1U|8|@$A|1V|B|1W|J|K]]|9|@]|C|$]]|$1|W|3|X|5|6|7|1X|8|@]|9|@]|C|$]]|$1|Y|3|Z|5|6|7|1Y|8|@]|9|@]|C|$]]|$1|10|3|-4|5|6|7|1Z|8|@]|9|@]|C|$]]]|11|$12|$5|13|14|15|C|$16|17]]]]

You should take a look at the <a href="http://seleniumhq.org/docs/02_selenium_basics.html#getting-started-choosing-your-selenium-tool" rel="noreferrer">documentation outlining the different parts of Selenium</a>. That's a good place to start as it guides you through the process of getting setup. Full disclosure, I help write the docs.

As for those downloads, the first link you have is the official releases for the project. The second link is the current beta builds, once they hit 2.0 they'll be on the site.

<ul>
<li>Selenium Core - more a component of selenium than a stand alone project. Without going into the project history, Selenium was once just a collection of .js files that automated a browser. No one uses these directly, they're just there for legacy reasons.</li>
<li>Selenium IDE - a firefox plugin for record/playback. You may want to start with this, to get used to the api, but you'll outgrow it soon</li>
<li>Selenium RC and when you do outgrow it, you'll use Selenium Remote Control. Selenium 1.x is a client-server architecture. You use the RC libraries to program tests that communicate with the server, and the server relays those commands to a browser. </li>
<li>Selenium Grid - a way to run Selenium testing on a distributed network of computers. Good for speeding things up once you've got a lot of tests.</li>
<li>Cubic Test - An eclipse-based tool that leverages selenium for testing. Not sure how popular it is.</li>
<li>Bromine - a web based script and test management tool. Uses selenium RC to run tests.</li>
</ul>

Then we get to the Selenium 2 beta. Selenium 2 is a major departure from the Selenium 1 model because it doesn't require a Selenium server. I say 'require' because it's optional to run the tests remotely on another computer. Selenium Server Standalone is the server you'd use for this. It's compatible with Selenium-RC as well as Selenium 2 for remote purposes.

You may have seen Selenium 2 referred to as WebDriver. WebDriver was another project that was merged a couple years ago and became the basis for Selenium 2. That's why Selenium 2 has a WebDriver interface, sometimes called the "WebDriver" api to distinguish from Selenium-RC.

If you're just starting out, I'd take a look at Selenium 2. It's getting 99.9% of the developer love right now, and the Selenium 1.x apis won't be advancing any further. As of January 2011 the Java libraries are the best supported, followed closely by .Net and Python/Ruby. Watir (the popular Ruby browser automation library) uses selenium under the hood if you want another api option.

On <a href="http://seleniumhq.org/download/" rel="nofollow noreferrer">Selenium download page</a>, there is a link to the Selenium RC (Remote Control).

On <a href="http://code.google.com/p/selenium/downloads/list" rel="nofollow noreferrer">another Selenium download page</a>, there are links for a Selenium RC 1.0.3, as well as Selenium 2 Server, sometimes also called Selenium 2 Standalone Server.

What is the difference between them?

If there are limitations, what are the limitations of each one?

Is the Selenium Server replacing the Remote Control?

Related question: <a href="https://stackoverflow.com/questions/4007819/selenium-remote-control-vs-webdriver">selenium remote control vs webdriver</a>

What is the difference between Selenium Remote Control and Selenium Server?

在上，有一个指向Selenium RC (远程控制)的链接。在上，有Selenium RC 1.0.3和Selenium 2Server的链接，Selenium 2Server有时也称为Selenium 2独立服务器。它们之间的区别是什么？如果有限制，那么每个限制都有什么限制？Selenium Server正在取代遥控...

问Selenium Remote Control和Selenium Server有什么区别？
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Selenium Remote Control和Selenium Server有什么区别？EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Selenium Remote Control和Selenium Server有什么区别？
EN