appium-mcp 0.0.1 → 1.1.5

package/src/resources/submodules/appium/packages/appium/docs/zh/intro/history.md

@@ -0,0 +1,196 @@
+---
+title: Appium Project History
+---
+
+Appium has been around in one form or another since 2012. It's been under the
+direction of various individuals and organizations, and it's even been
+implemented in 3 different programming languages! Welcome to more than you ever
+wanted to know about how Appium got to be what is it today...
+
+## Early Inspiration
+
+[Dan Cuellar](https://twitter.com/thedancuellar) was the Test Manager at Zoosk
+in 2011, when he encountered a problem. The length of the test passes on the
+iOS product was getting out of hand. Less testing was an option, but would come
+with additional risk, especially with it taking several days to get patches
+through the iOS App Store Review process. He thought back to his days working
+on websites and realized automation was the answer.
+
+Dan surveyed the existing landscape of tools, only to find that all of them
+hand major drawbacks. The tool supplied by Apple, UIAutomation, required tests
+to be written in JavaScript, and did not allow for real-time debugging or
+interpretation. It also had to be executed inside the Xcode profiling tool,
+Instruments. Other 3rd-party tools used private APIs and required SDKs and HTTP
+Servers to be embedded into the application. This seemed highly undesirable.
+
+Unsatisfied with the existing options, Dan asked his manager for some
+additional time to see if he could find a better way. He spent 2 weeks poking
+and prodding around to see if there was a way to use approved Apple
+technologies to automate an iOS application. The first implementation he tried
+used AppleScript to send messages to Mac UI elements using the OS
+X accessibility APIs. This worked to some degree, but would never work on real
+devices, not to mention other drawbacks.
+
+So he thought, what if I could get the UIAutomation framework to run in real
+time like an interpreter? He looked into it and he determined that all he would
+need to do is find a way to receive, execute, and reply to commands from within
+a UIAutomation javascript program. Using the utility Apple provided for
+executing shell commands he was able to `cat` sequentially ordered text files
+to receive commands, `eval()` the output to execute them, and write them back
+to disk with `python`. He then prepared code in C# that implemented the
+Selenium-style syntax to write the sequentially ordered javascript commands.
+iOSAuto is born.
+
+## Selenium Conference 2012
+
+Dan was selected to speak at Selenium Conference 2012 in London about an
+entirely different topic. As part of his presentation, he showed off iOS
+Automation using Selenium syntax to demonstrate writing platform-agnostic tests
+that use separate platform-specific page objects with a common interface. To
+his surprise, the cool test architecture would take a backseat to the spectacle
+of iOS tests running like WebDriver tests. Several people suggested that he
+give a lightning talk later in the conference to explain exactly how it worked.
+
+On the second day of the conference, Dan stepped up on stage to give the
+lightning talk.  Jason Huggins, co-creator of Selenium, moderated the lightning
+talks.  Dan experienced technical difficulties getting his presentation to
+load, and Jason nearly had to move on to the next lightning talk.  At the last
+moment, the screen turned on and Dan jumped into his presentation. He explained
+the details of his implementation and how it worked, begged for contributors,
+and in five minutes it was over. The crowd applauded politely, and he left the
+stage.
+
+## The Phone Rings
+
+Four months after the Selenium Conference, Jason called Dan. Jason had been
+working on iOS testing support for a client at Sauce Labs.  Jason remembered
+Dan's lightning talk and thought the project might be useful to Jason's work,
+but Dan's source code was not public. Jason asked Dan to meet up.  Later that
+week, Dan met Jason in a bar in San Francisco and showed him the source code
+for iOS Auto.
+
+A long-time open source advocate, Jason encouraged Dan to release his code
+under an open source license.  In August, Dan released the source
+code
+on GitHub in C#. Jason encouraged Dan to change the language to make the
+project more appealing to potential contributors. Dan uploaded a new version
+in
+Python.
+In September, Jason added a web server and began to implement the WebDriver
+wire
+protocol
+over HTTP, making iOS Auto scriptable from any Selenium WebDriver client
+library in any language.
+
+## The Mobile Testing Summit
+
+Jason decided that the project should be presented at the Mobile Testing
+Summit in November, but suggested that the
+project get a new name first. Many ideas were thrown out and they settled on
+AppleCart. A day later, while he was perusing some of Apple's guidance on
+copyright and trademarks, Jason noticed that under the section of examples for
+names Apple would defend its trademarks against, the first example was
+"AppleCart". He called Dan and informed him of the situation, and they
+brainstormed for a bit before Jason hit the jackpot. Appium... Selenium for
+Apps.
+
+## Sauce Labs and Node.js
+
+In January 2013, not long after the Mobile Testing Summit, Sauce Labs decided
+to fully back Appium and provide more developer power. A task force was created
+to evaluate the current state and how best to move forward with the project.
+The team, which included Jonathan Lipps (the current project lead), decided
+that Appium needed a rebirth, and ultimately settled on Node.js as the
+framework to use. Node is well-known as a fast and efficient web server
+backend, and at the end of the day, Appium is just a highly-specialized web
+server. It was also decided that JavaScript as a language was accessible enough
+that Appium would be able to grow into a larger community of open-source
+developers with JavaScript than the other options on the table.
+
+In just a few days, the team leveraged the existing work on Appium and had
+a new version of Appium with as much functionality as the previous Python
+version. The foundation had been laid for Appium's basic architecture, and we
+have been successfully building on it since. A few weeks into this sprint,
+Jonathan Lipps was formally designated project lead and he began to strategize
+how to get more people from the community involved with Appium's development.
+
+## Appium Around the World
+
+Ultimately, Jonathan decided that getting Appium in front of as many developers
+at conferences and meetups was the best way to attract users and contributions.
+Appium in its new incarnation was debuted at the Google Test Automation
+Conference 2013. Later in 2013,
+Appium was presented at conferences and meetups all around the US, as well as
+in England, Poland, Portugal, and Australia. Notably, Jonathan had Appium
+[perform as instruments in a band](https://www.youtube.com/watch?v=zsbNVkayYRQ)
+and Dan Cuellar put together a fun Appium video
+montage for Selenium Conference.
+
+But during all these presentations and conferences, the project continued to
+develop. Early in 2013 we released Android and Selendroid support, making
+Appium the first truly cross-platform automation framework. The project also
+continued to attract users and contributors, and by the end of 2013, we'd
+already had well over 1,000 commits.
+
+## The Road to Appium 1.0
+
+Appium began to grow and mature significantly. In May 2014,
+we released Appium 1.0, which stood as a milestone in Appium's development.
+Appium was given
+[various](https://www.prnewswire.com/news-releases/black-duck-announces-black-duck-open-source-rookies-of-the-year-winners-242383341.html)
+[awards](https://www.infoworld.com/article/2241247/164642-bossie-awards-2014-the-best-open-source-application-development-tools.html)
+and became the most popular open-source cross-platform mobile automation
+framework. Stability improved, bugs were prioritized and fixed, and features
+added. Sauce Labs increased the number of developers it donated to working
+on Appium, but the entire community stayed involved in guiding the project and
+contributing to it, and project governance continued to happen in the open, on
+public mailing lists and GitHub's issue tracker.
+
+## The Appium Umbrella Broadens
+
+Eventually, it became clear that the Appium codebase was not optimized for
+a large team of distributed, sometime contributors. We took the opportunity as
+a committer team to rewrite Appium from the ground up, using a more modern
+version of the JavaScript language, and redoing Appium's architecture so that
+it was easy for users or third-party developers to build their own Appium
+"drivers". We wanted for it to be easier for new contributors to get ramped up
+on the Appium codebase, and to see support for new platforms added to Appium by
+groups other than the core team. That vision has begun to be fulfilled, with
+groups like Microsoft and Youi.tv adding drivers to Appium for Windows desktop
+app automation and Youi.tv app automation, respectively.
+
+## Appium To The People
+
+In late 2016, Sauce Labs donated Appium as a project to the JS
+Foundation, in order to cement for the world Sauce's
+commitment that Appium remains open source. The JS Foundation is a non-profit
+open source stewardship organization which takes responsibility for holding the
+copyright for open source projects, as well as ensuring they have a long and
+successful tenure in the community. As a result of our move to a non-profit
+foundation, we hope that the door will open even more widely for new
+contributors, either as individuals or representing one of the many companies
+which now have an interest in seeing Appium move forward.
+
+Eventually, the JS Foundation merged into the [OpenJS Foundation](https://openjsf.org),
+and Appium became an Impact Project in the foundation.
+
+## Appium 2.0
+
+Appium 2 was released in 2023 and introduced an entirely revamped architecture, shifting focus to Appium
+as an ecosystem rather than an all-in-one project. This unlocked the ability for anyone to develop
+and share their own Appium extensions (drivers and plugins), opening up a world of possibilities
+for automation-related development for platforms far beyond iOS and Android! As a result,
+many third-party extensions were created, such as new drivers for Flutter and Windows, plugins for
+mocking APIs and managing device farms, new Appium clients based on Rust and Swift, and much more.
+
+Around this time was also when we started a sponsorship program for Appium, which attracted various
+major and minor sponsors alike. This allowed us to give back to the Appium community, by compensating
+contributors for their voluntary work on the project.
+
+## Appium 3.0
+
+2025 saw the release of Appium 3. This update was a lot smaller than Appium 2 and included only a
+few behavioral changes, instead focusing on removing deprecated code and updating compatibility for
+more modern ecosystems. Still, this reduced scope was also to be expected: since Appium 2, the
+main feature development efforts had shifted to individual drivers and plugins, many of which had
+gone through multiple major updates during the Appium 2 era.

package/src/resources/submodules/appium/packages/appium/docs/zh/intro/index.md

@@ -0,0 +1,39 @@
+---
+hide:
+  - toc
+
+title: Appium in a Nutshell
+---
+
+As mentioned on the main page, Appium aims to support UI automation of many _different platforms_
+(mobile, web, desktop, etc.). Not only that, but it also aims to support automation code written in
+_different languages_ (JS, Java, Python, etc.). Combining all of this functionality in a single
+program is a very daunting, if not impossible task!
+
+In order to achieve this, Appium is effectively split into four parts:
+
+<div class="grid cards" markdown>
+
+- :material-image-filter-center-focus-strong: **Appium Core** - defines the core APIs
+- :material-car: **Drivers** - implement connectivity to specific platforms
+- :octicons-code-16: **Clients** - implement Appium's API in specific languages
+- :fontawesome-solid-plug: **Plugins** - change or extend Appium's core functionality
+
+</div>
+
+Therefore, in order to start automating something with Appium, you need to:
+
+- Install Appium itself
+- Install a driver for your target platform
+- Install a client library for your target programming language
+- (Optional) install one or more plugins
+
+These are the basics! If you are ready to jump in, proceed with the [Quickstart](../quickstart/index.md)!
+
+If you wish to learn more details about how it all works, see these pages for background material:
+
+- [Appium Core](./appium.md)
+- [Appium Drivers](./drivers.md)
+- [Appium Clients](./clients.md)
+
+Finally, to learn about the origins of Appium, check out the [Appium Project History](./history.md).

package/src/resources/submodules/appium/packages/appium/docs/zh/quickstart/index.md

@@ -0,0 +1,23 @@
+---
+hide:
+  - toc
+
+title: 入门指南
+---
+
+让我们开始使用Appium！ 为了成功使用此快速入门，建议您首先阅读[介绍](../intro/index.md)，以便了解运行Appium和编写Appium脚本的概念。
+
+此快速入门的基本计划如下：
+
+1. 安装Appium
+2. 安装Appium驱动程序及其依赖项
+   - 本指南提供了[UiAutomator2 驱动程序](https://github.com/appium/appium-uiautomator2-driver) 的说明
+3. 在您选择的语言中安装Appium客户端库
+   - 本指南包含JavaScript、Python、Java、Ruby和.NET的选项
+4. 使用示例应用程序编写并运行简单的Appium自动化脚本
+
+### 系统需求
+
+在开始之前，请确保您的系统满足运行Appium服务器的[要求](../quickstart/requirements.md)。 其他要求将在安装UiAutomator2驱动程序时讨论。 本指南还假设您在平台上具有基本的命令行熟练度，例如能够运行命令、设置和持久化环境变量等...
+
+现在您准备开始了！ 前往安装[Appium](./install.md)。

package/src/resources/submodules/appium/packages/appium/docs/zh/quickstart/install.md

@@ -0,0 +1,47 @@
+---
+hide:
+  - toc
+
+title: 安装Appium
+---
+
+!!! 信息
+
+```
+安装前，请确保检查 [系统要求] (./requirements.md)。
+```
+
+Appium 可以使用 "npm" 在全局安装：
+
+```bash
+npm install -g appium
+```
+
+!!! 备注
+
+```
+目前不支持其他软件包管理。
+```
+
+## 启动Appium
+
+Appium 可以使用 [命令行](../reference/cli/index.md) 启动：
+
+```
+appium
+```
+
+这会启动Appium服务器进程，该进程加载所有已安装的Appium驱动程序，并开始等待来自客户端连接（如测试自动化脚本）的新会话请求。
+由于服务器进程独立于其客户端，因此必须在尝试启动新会话之前明确启动它。
+
+当服务器启动时，控制台日志将列出客户端可以用来连接到此服务器的所有有效URL：
+
+```
+[Appium] You can provide the following URLs in your client code to connect to this server:
+[Appium] 	http://127.0.0.1:4723/ (only accessible from the same host)
+(... any other URLs ...)
+```
+
+一旦客户端请求新会话，Appium服务器进程将开始记录此会话的所有详细信息，直到其终止。 请记住这一点——如果您遇到Appium测试的问题，您可以随时检查服务器日志以获取更多详细信息。
+
+接下来是什么？ 即使Appium已安装并运行，它也不捆绑任何驱动程序，这意味着它还不能自动化任何东西。 因此，我们将为Android设置自动化——继续[安装UiAutomator2驱动程序](./uiauto2-driver.md)。

package/src/resources/submodules/appium/packages/appium/docs/zh/quickstart/next-steps.md

@@ -0,0 +1,19 @@
+---
+hide:
+  - toc
+
+title: 下一步
+---
+
+现在您已成功为Android自动化设置了系统并运行了一个简单的测试，您将希望继续探索此文档。 特别是，这些是适合初学者的优秀指南和参考资料： 特别是，这些是适合初学者的优秀指南和参考资料：
+
+- [生态系统](../ecosystem/index.md) 页面：浏览可用的驱动程序、客户端、插件和工具
+- [管理Appium驱动程序和插件](../guides/managing-exts.md)
+- [功能](../guides/caps.md)
+- [设置](../guides/settings.md)
+
+您还会发现[Appium Inspector](https://github.com/appium/appium-inspector)是编写Appium测试不可或缺的工具，因为它允许对应用进行视觉检查，并帮助您发现测试脚本中使用的元素定位器。
+
+您还可以利用众多可用的在线Appium课程之一。
+
+祝您好运，玩得开心！

package/src/resources/submodules/appium/packages/appium/docs/zh/quickstart/requirements.md

@@ -0,0 +1,21 @@
+---
+hide:
+  - toc
+
+title: 系统要求
+---
+
+Appium 服务器的基本要求如下：
+
+- macOS、Linux 或 Windows 操作系统
+- [Node.js](https://nodejs.org) 版本在 [SemVer](https://semver.org) 范围 `^20.19.0 || ^22.12.0 || >=24.0.0`
+  - 推荐使用 LTS 版本
+- [`npm`](https://npmjs.com) 版本 `>=10`（`npm` 通常与 Node.js 捆绑，但可以独立升级）
+
+Appium 本身相对轻量，没有显著的磁盘空间或 RAM 要求。 即使在资源受限的环境如 Raspberry Pi 中，只要有 Node.js 就可以运行。
+
+### 驱动程序要求
+
+用于自动化特定平台的驱动程序可能有其他要求。 请参考该平台的 [Appium 驱动程序](../ecosystem/drivers.md) 文档以获取其他依赖项。 普遍的情况是，给定平台的 Appium 驱动程序需要安装该平台的开发者工具链和 SDK。
+
+为了帮助处理驱动程序要求，每个（官方）驱动程序都附带 Appium Doctor 工具，它允许验证是否已设置所有要求。 了解如何使用此工具的更多信息，请参阅 [命令行使用文档](../reference/cli/extensions.md#doctor)。

package/src/resources/submodules/appium/packages/appium/docs/zh/quickstart/test-dotnet.md

@@ -0,0 +1,99 @@
+---
+hide:
+  - toc
+
+title: 编写测试 (.NET)
+---
+
+[Appium .NET Client](https://github.com/appium/dotnet-client/) 是
+官方的 Appium C# 客户端。 这个驱动程序是 Selenium C# 客户端的扩展。 它具有常规驱动程序的所有功能，但在之上添加了 Appium 特定的方法。 该驱动程序在公共 NuGet Gallery 上作为 [Appium.WebDriver](https://www.nuget.org/packages/Appium.WebDriver/) 提供。
+
+现在，我们进入目录并创建一个新的 [NUnit](https://nunit.org/) 项目。 我们还将添加对 Appium.Net 驱动程序和其他依赖项的引用。
+
+```bash
+cd dotnet-client
+dotnet new nunit --name appiumtest
+
+cd appiumtest
+
+# 这将安装最新的 5.x 版本
+dotnet add package Appium.WebDriver  --prerelease
+dotnet add package Newtonsoft.Json --version 13.0.3
+```
+
+完成后，您的项目应该有一个占位符文件 `UnitTest1.cs`。 我们将替换代码以包含 OpenQA 命名空间、驱动程序的初始化以及实际测试。
+
+```C# title="UnitTest1.cs"
+using OpenQA.Selenium;
+using OpenQA.Selenium.Appium;
+using OpenQA.Selenium.Appium.Android;
+using OpenQA.Selenium.Appium.Enums;
+
+namespace appiumtest;
+
+public class Tests
+{
+    private AndroidDriver _driver;
+
+    [OneTimeSetUp]
+    public void SetUp()
+    {
+        var serverUri = new Uri(Environment.GetEnvironmentVariable("APPIUM_HOST") ?? "http://127.0.0.1:4723/");
+        var driverOptions = new AppiumOptions() {
+            AutomationName = AutomationName.AndroidUIAutomator2,
+            PlatformName = "Android",
+            DeviceName = "Android Emulator",
+        };
+
+        driverOptions.AddAdditionalAppiumOption("appPackage", "com.android.settings");
+        driverOptions.AddAdditionalAppiumOption("appActivity", ".Settings");
+        // NoReset assumes the app com.google.android is preinstalled on the emulator
+        driverOptions.AddAdditionalAppiumOption("noReset", true);
+
+        _driver = new AndroidDriver(serverUri, driverOptions, TimeSpan.FromSeconds(180));
+        _driver.Manage().Timeouts().ImplicitWait = TimeSpan.FromSeconds(10);
+    }
+
+    [OneTimeTearDown]
+    public void TearDown()
+    {
+        _driver.Dispose();
+    }
+
+    [Test]
+    public void TestFindApps()
+    {
+        _driver.StartActivity("com.android.settings", ".Settings");
+        _driver.FindElement(By.XPath("//*[@text='Apps']")).Click();
+    }
+}
+```
+
+!!! 备注
+
+```
+这份指南的范围不包括对 dotnet 客户端库或此处发生的一切进行完整说明，因此我们暂时不对代码本身进行详细解释。您可能需要特别阅读 Appium [Capabilities](../guides/caps.md)，以及熟悉 [dotnet 客户端驱动程序文档](https://github.com/appium/dotnet-client/) 以获得对您看到的各种 API 命令及其目的的更全面解释。
+```
+
+基本上，此代码执行以下操作：
+
+1. 定义一组"Capabilities"（参数）发送到 Appium 服务器，以便 Appium 知道您想要自动化什么。 有些参数可以使用环境变量覆盖。
+2. 在内置的 Android 设置应用上启动 Appium 会话。
+3. 查找"Apps"列表项并点击它。
+4. 结束 Appium 会话。
+
+就是这样！ 让我们试试。 在运行测试之前，请确保在另一个终端会话中运行 Appium 服务器，否则您会收到无法连接的错误。 然后，您可以执行脚本：
+
+```bash
+dotnet test
+
+# 示例输出：
+# Starting test execution, please wait...
+# A total of 1 test files matched the specified pattern.
+
+# Passed!  - Failed:     0, Passed:     1, Skipped:     0, Total:     1, Duration: 323 ms - appiumtest.dll (net7.0)
+```
+
+如果一切顺利，您将看到设置应用打开并在模拟器中导航到"Apps"视图，然后应用再次关闭。
+
+恭喜，您已经开始了 Appium 之旅！ 继续阅读一些 [后续步骤](./next-steps.md) 以进行探索。

package/src/resources/submodules/appium/packages/appium/docs/zh/quickstart/test-java.md

@@ -0,0 +1,20 @@
+---
+hide:
+  - toc
+
+title: 编写测试 (Java)
+---
+
+Appium 团队维护了一个官方的 [客户端](https://github.com/appium/java-client) 用于 Java 编程语言。
+它建立在 [Selenium](https://github.com/SeleniumHQ/selenium) 之上。
+您也可以在 Kotlin 项目中使用此客户端。
+
+按照 [将 Appium Java 客户端添加到您的测试框架](https://github.com/appium/java-client#add-appium-java-client-to-your-test-framework) 教程将库连接到您的测试框架源代码。
+
+Appium Java 客户端具有专用类来支持大多数官方 Appium 驱动程序。 对于其他驱动程序，您可以简单地使用 [AppiumDriver](https://github.com/appium/java-client/blob/master/src/main/java/io/appium/java_client/AppiumDriver.java) 类
+或从中构建自定义派生类。 查看 [驱动程序支持](https://github.com/appium/java-client#drivers-support) 文章以了解当前驱动程序类实现的更多信息。
+
+按照 [使用示例](https://github.com/appium/java-client#usage-examples) 文章以了解
+如何从您的测试框架调用 Java 客户端功能。
+
+一旦您成功运行了一个测试，您可以继续阅读一些 [后续步骤](./next-steps.md) 以进行探索。

package/src/resources/submodules/appium/packages/appium/docs/zh/quickstart/test-js.md

@@ -0,0 +1,62 @@
+---
+hide:
+  - toc
+
+title: 编写测试 (JS)
+---
+
+要在 JavaScript (Node.js) 中编写 Appium 测试，我们需要选择一个与 Appium 兼容的客户端库。 维护最好的库，也是 Appium 团队推荐使用的，是 [WebdriverIO](https://webdriver.io)，所以让我们使用它。 由于我们已经安装了 Appium，我们知道我们的 Node 和 NPM 已经满足要求。 所以在您的计算机上某个地方创建一个新的项目目录，然后在其中初始化一个新的 Node.js 项目：
+
+```bash
+npm init
+```
+
+提示中输入什么并不重要，只要最终得到一个有效的 `package.json`。
+
+现在，通过 NPM 安装 `webdriverio` 包：
+
+```bash
+npm i --save-dev webdriverio
+```
+
+完成后，您的 `package.json` 文件应该包含如下部分：
+
+```json title="package.json"
+--8<-- "./sample-code/quickstarts/js/package.json"
+```
+
+现在是编写测试本身的时候了。 创建一个名为 `test.js` 的新文件，内容如下：
+
+```js title="test.js"
+--8<-- "./sample-code/quickstarts/js/test.js"
+```
+
+!!! note
+
+```
+这份指南的范围不包括对 WebdriverIO 客户端库或此处发生的一切进行完整说明，因此我们暂时不对代码本身进行详细解释。您可能需要特别阅读 Appium [Capabilities](../guides/caps.md)，以及熟悉优秀的 [WebdriverIO 文档](https://webdriver.io/docs/gettingstarted) 以获得对您看到的各种 API 命令及其目的的更全面解释。
+```
+
+!!! note
+
+```
+示例代码可从 [GitHub Appium 仓库](https://github.com/appium/appium/tree/master/packages/appium/sample-code/quickstarts/js) 获取。
+```
+
+基本上，此代码执行以下操作：
+
+1. 定义一组"Capabilities"（参数）发送到 Appium 服务器，以便 Appium 知道您想要自动化什么。
+2. 在内置的 Android 设置应用上启动 Appium 会话。
+3. 查找"Apps"列表项并点击它。
+4. 暂停片刻纯粹为了视觉效果。
+5. 结束 Appium 会话。
+
+就是这样！ 让我们试试。 在运行测试之前，请确保在另一个终端会话中运行 Appium 服务器，否则您会收到无法连接的错误。 然后，您可以执行脚本：
+
+```bash
+node test.js
+```
+
+如果一切顺利，您将看到设置应用打开并导航到"Apps"视图，然后应用再次关闭。
+
+恭喜，您已经开始了 Appium 之旅！ 继续阅读一些 [后续步骤](./next-steps.md) 以进行探索。

package/src/resources/submodules/appium/packages/appium/docs/zh/quickstart/test-py.md

@@ -0,0 +1,57 @@
+---
+hide:
+  - toc
+
+title: 编写测试 (Python)
+---
+
+[Appium Python Client](https://github.com/appium/python-client) 是
+官方的 Python Appium 客户端，可通过 pypi 以 [Appium-Python-Client](https://pypi.org/project/Appium-Python-Client/) 包名获取。
+它继承自 [Selenium Python Binding](https://pypi.org/project/selenium/)，
+因此安装 Appium Python Client 包括 selenium 绑定。
+
+```bash
+pip install Appium-Python-Client
+```
+
+此示例使用 Python 的内置 `unittest` 模块，您也可以使用任何您想要的 Python 测试框架。
+Appium Python 客户端自动添加 `appium:` 前缀。
+您通常不需要担心前缀。
+
+```python title="test.py"
+--8<-- "./sample-code/quickstarts/py/test.py"
+```
+
+!!! note
+
+```
+这份指南的范围不包括对 Python 客户端库或此处发生的一切进行完整说明，因此我们暂时不对代码本身进行详细解释。
+
+- 您可能需要特别阅读 Appium [Capabilities](../guides/caps.md)。
+- Python Client GitHub 仓库中的 [功能测试代码](https://github.com/appium/python-client/tree/master/test/functional) 应该有助于找到更多工作示例。
+- [文档](https://appium.github.io/python-client-sphinx/) 也有助于找到 Appium Python Client 中定义的方法。
+```
+
+!!! note
+
+```
+示例代码可从 [GitHub Appium 仓库](https://github.com/appium/appium/tree/master/packages/appium/sample-code/quickstarts/py) 获取。
+```
+
+基本上，此代码执行以下操作：
+
+1. 定义一组"Capabilities"（参数）发送到 Appium 服务器，以便 Appium 知道您想要自动化什么。
+2. 在内置的 Android 设置应用上启动 Appium 会话。
+3. 查找"Apps"列表项并点击它。
+4. 暂停片刻纯粹为了视觉效果。
+5. 结束 Appium 会话。
+
+就是这样！ 让我们试试。 在运行测试之前，请确保在另一个终端会话中运行 Appium 服务器，否则您会收到无法连接的错误。 然后，您可以执行脚本：
+
+```bash
+python test.py
+```
+
+如果一切顺利，您将看到设置应用打开并导航到"Apps"视图，然后应用再次关闭。
+
+恭喜，您已经开始了 Appium 之旅！ 继续阅读一些 [后续步骤](./next-steps.md) 以进行探索。

package/src/resources/submodules/appium/packages/appium/docs/zh/quickstart/test-rb.md

@@ -0,0 +1,80 @@
+---
+hide:
+  - toc
+
+title: 编写测试 (Ruby)
+---
+
+[AppiumLib](https://github.com/appium/ruby_lib) 和 [AppiumLibCore](https://github.com/appium/ruby_lib_core)（**推荐**）是 Ruby 中的官方 Appium 客户端库，可通过 gem 以 [appium_lib](https://rubygems.org/gems/appium_lib) 和 [appium_lib_core](https://rubygems.org/gems/appium_lib_core) 包名获取。 appium_lib_core 继承自 Selenium Ruby Binding，而 appium_lib 继承自 appium_lib_core，因此安装这些库包括 selenium 绑定。 如果您需要一个不太复杂的客户端解决方案，我们推荐 `appium_lib_core`。 `appium_lib` 有一些核心没有的有用方法，但代价是更大的复杂性和可能在最新环境中不工作的历史方法。
+
+作为第一步，让我们初始化一个 Gemfile 来管理依赖项：
+
+```bash
+bundle init
+```
+
+然后，您可以如下添加 Appium Ruby Client 依赖项：
+
+```bash
+bundle add appium_lib_core
+# or
+# bundle add appium_lib
+```
+
+下面的测试代码示例使用 `test-unit` 模块，因此请运行：
+
+```bash
+bundle add test-unit
+```
+
+一旦这些步骤完成，您的 `Gemfile` 文件应该包含：
+
+```ruby title="Gemfile"
+--8<-- "./sample-code/quickstarts/rb/Gemfile"
+```
+
+`appium_lib_core` 是作为 Appium 客户端的主要部分。
+`appium_lib` 有各种辅助方法，但驱动程序实例通常被设计为全局变量使用。 它可能导致处理实例的问题。
+`appium_lib_core` 没有这样的全局变量。
+
+此示例使用 `appium_lib_core` 和 `test-unit` gem 模块。
+在 `appium_lib` 中的测试代码应该类似。
+
+```ruby title="test.rb"
+--8<-- "./sample-code/quickstarts/rb/test.rb"
+```
+
+!!! note
+
+```
+这份指南的范围不包括对 Ruby 客户端库或此处发生的一切进行完整说明，因此我们暂时不对代码本身进行详细解释。
+
+- 您可能需要特别阅读 Appium [Capabilities](../guides/caps.md)。
+- appium_lib_core GitHub 仓库中的 [功能测试代码](https://github.com/appium/ruby_lib_core/tree/master/test/functional) 应该有助于找到更多工作示例。
+- 文档 [appium_lib_core](https://www.rubydoc.info/github/appium/ruby_lib_core) 和 [appium_lib](https://www.rubydoc.info/github/appium/ruby_lib) 也有助于找到可用方法。
+```
+
+!!! note
+
+```
+示例代码可从 [GitHub Appium 仓库](https://github.com/appium/appium/tree/master/packages/appium/sample-code/quickstarts/rb) 获取。
+```
+
+基本上，此代码执行以下操作：
+
+1. 定义一组"Capabilities"（参数）发送到 Appium 服务器，以便 Appium 知道您想要自动化什么。
+2. 在内置的 Android 设置应用上启动 Appium 会话。
+3. 查找"Apps"列表项并点击它。
+4. 暂停片刻纯粹为了视觉效果。
+5. 结束 Appium 会话。
+
+就是这样！ 让我们试试。 在运行测试之前，请确保在另一个终端会话中运行 Appium 服务器，否则您会收到无法连接的错误。 然后，您可以执行脚本：
+
+```bash
+# 如果您的环境尚未运行安装命令，请先运行 "bundle install"。
+bundle exec ruby test.rb
+```
+
+如果一切顺利，您将看到设置应用打开并导航到"Apps"视图，然后应用再次关闭。
+
+恭喜，您已经开始了 Appium 之旅！ 继续阅读一些 [后续步骤](./next-steps.md) 以进行探索。