Selenium 远程控制和 Selenium 服务器有什么区别?

发布于 2024-10-13 21:42:34 字数 555 浏览 3 评论 0原文

Selenium下载页面上,有一个指向Selenium RC(远程控制)的链接)。

另一个 Selenium 下载页面上,有 Selenium RC 的链接1.0.3,以及Selenium 2 Server,有时也称为Selenium 2 Standalone Server

它们之间有什么区别?

如果有限制,那么每一项的限制是什么?

Selenium 服务器正在取代远程控制吗?

相关问题: selenium 远程控制与 webdriver

On Selenium download page, there is a link to the Selenium RC (Remote Control).

On another Selenium download page, 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: selenium remote control vs webdriver

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(2

横笛休吹塞上声 2024-10-20 21:42:34

您应该查看文档,其中概述了硒。这是一个很好的起点,因为它会指导您完成设置过程。完全披露,我帮助编写文档。

至于这些下载,您拥有的第一个链接是该项目的官方版本。第二个链接是当前的测试版本,一旦达到 2.0,它们就会出现在网站上。

  • Selenium Core - 更多的是 selenium 的一个组件,而不是一个独立的项目。如果不深入了解项目历史,Selenium 曾经只是自动化浏览器的 .js 文件的集合。没有人直接使用它们,它们只是出于遗留原因而存在。
  • Selenium IDE - 用于录制/播放的 Firefox 插件。您可能想从这里开始,以习惯 API,但您很快就会不再需要
  • Selenium RC,当您不再需要它时,您将使用 Selenium Remote Control。 Selenium 1.x 是一种客户端-服务器架构。您可以使用 RC 库对与服务器通信的测试进行编程,然后服务器将这些命令中继到浏览器。
  • Selenium Grid - 一种在分布式计算机网络上运行 Selenium 测试的方法。一旦您进行了大量测试,这对于加快速度很有帮助。
  • Cubic Test - 一个基于 eclipse 的工具,利用 selenium 进行测试。不确定它有多受欢迎。
  • Bromine - 一个基于 Web 的脚本和测试管理工具。使用 selenium RC 来运行测试。

然后我们进入Selenium 2 beta。 Selenium 2 与 Selenium 1 模型有很大不同,因为它不需要 Selenium 服务器。我说“需要”是因为可以选择在另一台计算机上远程运行测试。 Selenium Server Standalone 是您用于此目的的服务器。它与 Selenium-RC 以及 Selenium 2 兼容用于远程目的。

您可能已经看到 Selenium 2 被称为 WebDriver。 WebDriver 是几年前合并的另一个项目,成为 Selenium 2 的基础。这就是为什么 Selenium 2 有一个 WebDriver 接口,有时称为“WebDriver”api 以区别于 Selenium-RC。

如果您刚刚开始,我会看一下 Selenium 2。它现在受到 99.9% 的开发人员的喜爱,Selenium 1.x api 不会再进一步​​发展。截至 2011 年 1 月,Java 库得到了最好的支持,紧随其后的是 .Net 和 Python/Ruby。如果您想要另一个 api 选项,Watir(流行的 Ruby 浏览器自动化库)会在底层使用 selenium。

You should take a look at the documentation outlining the different parts of Selenium. 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.

  • 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.
  • 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
  • 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.
  • 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.
  • Cubic Test - An eclipse-based tool that leverages selenium for testing. Not sure how popular it is.
  • Bromine - a web based script and test management tool. Uses selenium RC to run tests.

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.

少年亿悲伤 2024-10-20 21:42:34

Selenium 网站上的文档说远程控制由

  • 服务器
  • 客户端库

服务器负责执行实际工作(在浏览器中执行操作),而您的操作规范(执行控制)来自不同的库

这称为“远程控制”,因为服务器不必部署在执行实际脚本的同一台计算机上。这些脚本可以通过网络连接到远程 selenium 服务器并执行操作。

总而言之,当您使用 Selenium Remote Control 时,您正在使用服务器 + 客户端库。它们应该一起使用。

我不知道 Selenium 2 是否也会如此,或者他们是否正在改变一些事情。我只相信 Selenium 1 就是这样工作的。

The documentation on Selenium's website says that the Remote Control consist of

  • a server
  • client libraries

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.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文