mirror of
https://github.com/appium/appium.git
synced 2026-02-22 03:08:47 -06:00
docs(appium): Update documentation translations (#21621)
Co-authored-by: mykola-mokhnach <7767781+mykola-mokhnach@users.noreply.github.com>
This commit is contained in:
committed by
GitHub
parent
dd01c57da6
commit
5568749990
@@ -1,5 +1,5 @@
|
||||
INHERIT: ./base-mkdocs.yml
|
||||
site_url: https://appium.io/docs/zh
|
||||
site_url: https://appium.io/docs/cn
|
||||
edit_uri: edit/master/packages/appium/docs/zh
|
||||
site_description: Appium自动化项目文档
|
||||
docs_dir: zh
|
||||
@@ -9,40 +9,40 @@ theme:
|
||||
nav:
|
||||
- 欢迎使用: index.md
|
||||
- 博客: blog/index.md
|
||||
- 简介:
|
||||
- 简介:
|
||||
- intro/index.md
|
||||
- 背景:
|
||||
- 背景:
|
||||
- intro/appium.md
|
||||
- intro/drivers.md
|
||||
- intro/clients.md
|
||||
- intro/history.md
|
||||
- 快速开始:
|
||||
- 快速开始:
|
||||
- quickstart/index.md
|
||||
- quickstart/requirements.md
|
||||
- quickstart/install.md
|
||||
- quickstart/uiauto2-driver.md
|
||||
- 写一个测试:
|
||||
- 写一个测试:
|
||||
- quickstart/test-js.md
|
||||
- quickstart/test-py.md
|
||||
- quickstart/test-java.md
|
||||
- quickstart/test-rb.md
|
||||
- quickstart/test-dotnet.md
|
||||
- quickstart/next-steps.md
|
||||
- 生态系统:
|
||||
- 生态系统:
|
||||
- ecosystem/index.md
|
||||
- ecosystem/drivers.md
|
||||
- ecosystem/clients.md
|
||||
- ecosystem/plugins.md
|
||||
- ecosystem/tools.md
|
||||
- Reference:
|
||||
- 参考:
|
||||
- reference/index.md
|
||||
- Command Line Interface:
|
||||
- 命令行界面:
|
||||
- reference/cli/index.md
|
||||
- reference/cli/server.md
|
||||
- reference/cli/extensions.md
|
||||
- reference/cli/setup.md
|
||||
- reference/cli/env-vars.md
|
||||
- API Endpoints:
|
||||
- API 端点:
|
||||
- reference/api/index.md
|
||||
- reference/api/webdriver.md
|
||||
- reference/api/bidi.md
|
||||
@@ -51,11 +51,11 @@ nav:
|
||||
- reference/api/appium.md
|
||||
- reference/api/others.md
|
||||
- reference/api/plugins.md
|
||||
- 指南:
|
||||
- 迁移:
|
||||
- 指南:
|
||||
- 迁移:
|
||||
- guides/migrating-2-to-3.md
|
||||
- guides/migrating-1-to-2.md
|
||||
- 服务器/驱动程序配置:
|
||||
- 服务器/驱动程序配置:
|
||||
- guides/managing-exts.md
|
||||
- guides/branch-testing.md
|
||||
- guides/config.md
|
||||
@@ -65,24 +65,24 @@ nav:
|
||||
- guides/grid.md
|
||||
- guides/caching.md
|
||||
- guides/tls.md
|
||||
- 会话配置:
|
||||
- 会话配置:
|
||||
- guides/caps.md
|
||||
- guides/settings.md
|
||||
- guides/execute-methods.md
|
||||
- guides/context.md
|
||||
- guides/event-timing.md
|
||||
- More Resources:
|
||||
- 更多资源:
|
||||
- resources/index.md
|
||||
- 开发:
|
||||
- 开发:
|
||||
- developing/index.md
|
||||
- developing/build-drivers.md
|
||||
- developing/build-plugins.md
|
||||
- developing/build-docs.md
|
||||
- developing/build-doctor-checks.md
|
||||
- developing/sensitive.md
|
||||
- 开发者参考:
|
||||
- 开发者参考:
|
||||
- developing/config-system.md
|
||||
- Contributing:
|
||||
- 贡献:
|
||||
- contributing/index.md
|
||||
- Sponsors:
|
||||
- 赞助者:
|
||||
- sponsors/index.md
|
||||
|
||||
@@ -1,63 +1,54 @@
|
||||
---
|
||||
hide:
|
||||
- navigation
|
||||
- 导航栏
|
||||
|
||||
title: ""
|
||||
title: 对Appium 的贡献
|
||||
---
|
||||
|
||||
As such, we welcome contributions!
|
||||
Appium项目离不开来自公司和志愿者的代码、文档、维护和支持的众多贡献。 因此,我们欢迎贡献!
|
||||
|
||||
There are a lot of different ways to help the project - see below for everything you can do and the
|
||||
processes to follow for each contribution method. 加入讨论论坛
|
||||
有许多不同的方式可以帮助项目——请参阅下方了解您可以做的一切以及每个贡献方法的流程。 请注意,无论您如何贡献,您的参与都受我们的[行为准则](https://github.com/appium/appium/blob/master/CONDUCT.md)管辖。
|
||||
|
||||
## 你无需了解 Appium 的内部实现就能做出贡献!如果你有使用 Appium 的经验并愿意分享,请考虑在 Appium 论坛(discuss.appium.io)帮助其他用户。去看看是否有你能回答的问题。
|
||||
## 加入讨论论坛
|
||||
|
||||
报告错误或功能请求 如果你遇到错误,或有希望 Appium 支持的新功能,请在我们的 GitHub issue 跟踪器中告知我们。创建 issue 时请使用合适的问题表单模板。
|
||||
您不需要了解Appium的内部机制就能做出贡献! 如果您有使用Appium的经验,并愿意与他人分享您的知识,请考虑在Appium论坛[discuss.appium.io](https://discuss.appium.io/)上帮助用户。 快去看看是否有您能回答的问题。
|
||||
|
||||
## 除了创建 issue 之外,你还可以帮助我们调查已报告的问题。你只需对 Appium 有足够的熟悉度以便尝试复现 bug。
|
||||
## 报告错误或功能请求
|
||||
|
||||
If you've encountered a bug, or have a cool feature in mind that you think Appium should support,
|
||||
make sure to let us know at our [GitHub issue tracker](https://github.com/appium/appium/issues).
|
||||
你无需了解 Appium 的内部实现也可以参与贡献!如果你有使用 Appium 的经验并愿意分享,请考虑在 Appium 论坛(discuss.appium.io)帮助其他用户。去看看是否有你可以回答的问题。
|
||||
如果您遇到了一个bug,或者有一个很酷的功能想法,认为Appium应该支持,请务必在我们的[GitHub issue tracker](https://github.com/appium/appium/issues)上告诉我们。
|
||||
请在创建issue时使用适当的issue表单模板。
|
||||
|
||||
## 报告缺陷或功能需求
|
||||
## 对问题分类
|
||||
|
||||
如果你遇到错误,或有希望 Appium 支持的新功能想法,请在我们的 GitHub 问题跟踪器中告诉我们。创建问题时请使用相应的问题表单模版。 问题分级(Triage Issues)
|
||||
除了创建issue,您还可以帮助我们调查已报告的问题。 您只需要对Appium有足够的熟悉程度来尝试重现bug。
|
||||
|
||||
除了创建问题,你也可以帮助我们调查已报告的问题。你只需对 Appium 有足够的熟悉度以尝试重现这些问题。
|
||||
您可以通过检查我们的[GitHub issue tracker](https://github.com/appium/appium/issues)中带有标签如`Needs Triage`或`Needs Info`的问题开始,并留下相关评论:
|
||||
|
||||
- If the issue is a duplicate, drop a link to the original issue
|
||||
- 需要分类(Needs Triage)
|
||||
- 需要信息(Needs Info)
|
||||
- 如果问题是重复的,请提供指向原始issue的链接
|
||||
- 如果用户没有提供足够的信息(如Appium日志),请向他们询问更多细节
|
||||
- 如果您能在自己的环境中重现问题,请提供您认为有助于我们追踪问题原因的所有信息
|
||||
|
||||
如果该问题是重复的,请附上原始问题的链接
|
||||
有关对Appium问题进行分类的更多信息(适用于任何Appium项目仓库),请联系[技术委员会](https://github.com/appium/appium/blob/master/GOVERNANCE.md#the-technical-committee)的任何成员。
|
||||
|
||||
## 如果用户未提供足够的信息(例如 Appium 日志),请向他们索取更多细节
|
||||
## 贡献代码
|
||||
|
||||
如果你能在自己的环境中重现该问题,请提供所有你认为有助于我们查找原因的信息
|
||||
我们始终欢迎用于改进Appium代码或文档的拉取请求!
|
||||
|
||||
!!! info
|
||||
|
||||
关于为 Appium(任何 Appium 项目仓库)进行问题分类的更多信息,请联系任意一位技术委员会成员。
|
||||
开发者信息可能不像面向用户的信息那样频繁更新,或者它在在线仓库中的当前形式可能最相关,而不是在这个发布的版本中。请务必检查仓库或与维护者讨论。我们很乐意帮助新贡献者入门!
|
||||
|
||||
贡献代码
|
||||
|
||||
```sh
|
||||
我们欢迎通过拉取请求(pull requests)来改进 Appium 的代码或文档!
|
||||
```
|
||||
|
||||
!!! info
|
||||
|
||||
开发者信息可能不会像面向用户的信息那样频繁更新,或在当前发布版本中并非始终适用。请务必查看在线仓库或与维护者讨论。我们很乐意帮助新贡献者入门!
|
||||
|
||||
首先克隆仓库(推荐先 fork):
|
||||
首先克隆仓库(我们建议先[fork](https://github.com/appium/appium/fork)
|
||||
它):
|
||||
|
||||
```sh
|
||||
git clone https://github.com/appium/appium.git
|
||||
cd appium
|
||||
```
|
||||
|
||||
如果你是 VS Code 用户,可以使用 [Runme](https://runme.dev/api/runme?repository=https%3A%2F%2Fgithub.com%2Fappium%2Fappium.git&fileToOpen=packages%2Fappium%2Fdocs%2Fen%2Fcontributing%2Findex.md) 轻松检出该项目。
|
||||
!!! info
|
||||
|
||||
如果您是 VS Code 用户,您可以使用 [Runme](https://runme.dev/api/runme?repository=https%3A%2F%2Fgithub.com%2Fappium%2Fappium.git&fileToOpen=packages%2Fappium%2Fdocs%2Fen%2Fcontributing%2Findex.md) 轻松地查看项目。
|
||||
|
||||
安装依赖:
|
||||
|
||||
@@ -67,64 +58,75 @@ npm install
|
||||
|
||||
接下来你可以做几件事情。
|
||||
|
||||
```sh
|
||||
构建项目:
|
||||
```
|
||||
|
||||
```sh
|
||||
npm run build
|
||||
|
||||
```sh
|
||||
构建项目并监听更改:
|
||||
```
|
||||
|
||||
构建项目并监视更改:
|
||||
|
||||
```sh
|
||||
npm run dev
|
||||
|
||||
```sh
|
||||
|
||||
```
|
||||
|
||||
启动本地 Appium 服务器:
|
||||
|
||||
```sh
|
||||
npm start
|
||||
|
||||
```sh
|
||||
运行各种测试:
|
||||
```
|
||||
|
||||
### npm run lint
npm run test:unit
npm run test:types
npm run test:smoke
npm run test:e2e
npm run test:quick # unit 和 types
npm run test:slow # 全部测试
|
||||
运行测试:
|
||||
|
||||
你也可以为特定工作区运行测试,例如:
|
||||
```sh
|
||||
npm run lint
|
||||
npm run test:unit
|
||||
npm run test:types
|
||||
npm run test:smoke
|
||||
npm run test:e2e
|
||||
npm run test:quick # unit and types
|
||||
npm run test:slow # everything
|
||||
```
|
||||
|
||||
您也可以运行特定工作区的测试,例如:
|
||||
|
||||
```sh
|
||||
export APPIUM_WORKSPACE=@appium/base-driver
|
||||
npm run test:unit -w $APPIUM_WORKSPACE 文档
|
||||
|
||||
本项目的文档位于项目仓库中,采用 Markdown 文件形式,由 @appium/docutils 模块的文档系统构建。该模块基于 MkDocs,因此需要在系统上安装 Python。
|
||||
|
||||
```sh
|
||||
@appium/docutils
|
||||
npm run test:unit -w $APPIUM_WORKSPACE
|
||||
```
|
||||
|
||||
### 文档
|
||||
|
||||
此项目的文档位于项目[仓库本身](https://github.com/appium/appium/tree/master/packages/appium/docs)中。
|
||||
它包含在Markdown文件中,这些文件由`@appium/docutils`模块中的文档系统构建。 该模块基于[MkDocs](https://www.mkdocs.org/),因此需要在您的系统上安装[Python](https://www.python.org/)。
|
||||
|
||||
安装 Python 依赖:
|
||||
|
||||
```sh
|
||||
npm run install-docs-deps
|
||||
```
|
||||
|
||||
在完成修改后,你可以以开发模式运行文档服务器:
|
||||
安装 Python 依赖:
|
||||
|
||||
## npm run dev:docs
|
||||
```sh
|
||||
npm run dev:docs
|
||||
```
|
||||
|
||||
然后可以在 http://127.0.0.1:8000/docs/en 查看文档。 http://127.0.0.1:8000/docs/en
|
||||
然后你可以在 `http://127.0.1:8000/docs/en` 中查看文档。
|
||||
|
||||
### 如果你希望参与将 Appium 文档翻译成你的语言,请加入 Appium Documentation Crowdin 项目的翻译者组并开始翻译。如果你发现可用的 Crowdin 语言列表中缺少你的语言,请创建 issue 告知我们。
|
||||
## 翻译Appium 文档
|
||||
|
||||
Appium 文档翻译(非英语语言)的流程是自动化的,由 Crowdin 翻译管理系统完成。不要直接在 GitHub 上编辑任何已翻译的文档,因为它们将在即将的同步中被 Crowdin 导出的版本覆盖。 从何开始
|
||||
Appium文档本地化为英语以外语言的过程是自动化的,通过[Crowdin翻译管理系统](https://crowdin.com)完成。 请勿直接在GitHub Appium仓库中编辑任何翻译文档,因为它们将在即将进行的同步中被从Crowdin导出的文档替换。
|
||||
|
||||
### Source Language Updates
|
||||
### 从哪里开始
|
||||
|
||||
Changes in documents are synchronized to Crowdin automatically via the `Update Crowdin English Docs` GitHub action.
|
||||
This action is triggered automatically as soon as there are any changes under `packages/appium/docs/en/**.md`
|
||||
or `packages/appium/docs/mkdocs-en.yml`.
|
||||
如果您想为Appium文档翻译成您的语言做出贡献,只需加入[Appium Documentation](https://crowdin.com/project/appium-documentation) Crowdin项目的翻译者组,然后在那里开始翻译文档。 如果您看到您的语言在Crowdin可用语言列表中缺失,请通过创建[issue](https://github.com/appium/appium/issues)告诉我们。
|
||||
|
||||
### Fetching Translated Documents
|
||||
### 源语言更新
|
||||
|
||||
In order to fetch translated files from Crowdin to the GitHub repository it is necessary to trigger
|
||||
the `Sync Crowdin Docs Translations` action. This action should also automatically create a PR with
|
||||
corresponding translated resources included.
|
||||
文档中的更改通过 `Update Crowdin English Docs GitHub` action自动同步到Crowdin。
|
||||
一旦 `packages/appium/docs/en/**.md` 或 `packages/appium/docs/mkdocs-en.yml` 下有任何更改,此action就会自动触发。
|
||||
|
||||
### 获取翻译文档
|
||||
|
||||
为了从Crowdin获取翻译文件到GitHub仓库,需要触发 `Sync Crowdin Docs Translations` action。 此action还会自动创建一个包含相应翻译资源的PR。
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
hide:
|
||||
- navigation
|
||||
- 导航栏
|
||||
- toc
|
||||
|
||||
title: 欢迎使用
|
||||
@@ -44,11 +44,11 @@ title: 欢迎使用
|
||||
- 查看 [**简介**](./intro/index.md) 以确保您理解关键概念
|
||||
- 通过 [**快速开始**](./quickstart/index.md) 来设置并运行一个基本的 Android 测试
|
||||
- 访问 [**生态系统**](./ecosystem/index.md) 页面,获取您可能想要使用的驱动程序、客户端和插件列表
|
||||
- Consult the [**Reference**](./reference/index.md) page for information on the Appium CLI and supported endpoints
|
||||
- Read the different [**Guides**](./guides/migrating-2-to-3.md) for a variety of instructions, tips and tricks
|
||||
- Check out various third-party [**Resources**](./resources/index.md) to explore Appium around the web
|
||||
- 访问 [**Reference**](./reference/index.md) 页面获取Appium CLI 和支持的端点信息
|
||||
- 阅读不同版本的 [**指南**](./guides/migrating-2-to-3.md),了解各版本的说明、提示和技巧
|
||||
- 查看各种第三方 [**资源**](./resources/index.md) 以探索网络上的 Appium
|
||||
- 要创建自己的 Appium 扩展,请参阅 [**开发者**](./developing/index.md) 文档
|
||||
- For contributions to Appium itself, refer to the [**Contributing**](./contributing/index.md) page
|
||||
- Have a look at the [**Appium Blog**](./blog/index.md) to learn what's new in the project
|
||||
- 有关对 Appium 的贡献,请查阅 [**贡献**](./contributing/index.md) 页面
|
||||
- 查看 [**Appium博客**](./blog/index.md) ,了解项目中的新内容
|
||||
|
||||
</div>
|
||||
|
||||
@@ -2,28 +2,22 @@
|
||||
hide:
|
||||
- toc
|
||||
|
||||
title: Getting Started
|
||||
title: 入门指南
|
||||
---
|
||||
|
||||
Let's get up and running with Appium! To successfully use this quickstart, it's recommended that
|
||||
you first have read the [Introduction](../intro/index.md), so that you understand the concepts involved in
|
||||
running Appium and writing Appium scripts.
|
||||
让我们开始使用Appium! 为了成功使用此快速入门,建议您首先阅读[介绍](../intro/index.md),以便了解运行Appium和编写Appium脚本的概念。
|
||||
|
||||
The basic plan for this quickstart is as follows:
|
||||
此快速入门的基本计划如下:
|
||||
|
||||
1. Install Appium
|
||||
2. Install an Appium driver and its dependencies
|
||||
- This guide provides instructions for the [UiAutomator2 driver](https://github.com/appium/appium-uiautomator2-driver)
|
||||
3. Install an Appium client library in your language of choice
|
||||
- This guide contains options for JavaScript, Python, Java, Ruby, and .NET
|
||||
4. Write and run a simple Appium automation script using a sample application
|
||||
1. 安装Appium
|
||||
2. 安装Appium驱动程序及其依赖项
|
||||
- 本指南提供了[UiAutomator2 驱动程序](https://github.com/appium/appium-uiautomator2-driver) 的说明
|
||||
3. 在您选择的语言中安装Appium客户端库
|
||||
- 本指南包含JavaScript、Python、Java、Ruby和.NET的选项
|
||||
4. 使用示例应用程序编写并运行简单的Appium自动化脚本
|
||||
|
||||
### Requirements
|
||||
### 系统需求
|
||||
|
||||
Before getting started, make sure your system satisfies the
|
||||
[requirements](../quickstart/requirements.md) for running the Appium server. Additional requirements
|
||||
will be discussed in conjunction with installing the UiAutomator2 driver. The guide also assumes
|
||||
you have basic command line proficiency on your platform, for example being able to run commands, set
|
||||
and persist environment variables, etc...
|
||||
在开始之前,请确保您的系统满足运行Appium服务器的[要求](../quickstart/requirements.md)。 其他要求将在安装UiAutomator2驱动程序时讨论。 本指南还假设您在平台上具有基本的命令行熟练度,例如能够运行命令、设置和持久化环境变量等...
|
||||
|
||||
Now you're ready to get started! So head on over to [Installing Appium](./install.md).
|
||||
现在您准备开始了! 前往安装[Appium](./install.md)。
|
||||
|
||||
@@ -2,42 +2,39 @@
|
||||
hide:
|
||||
- toc
|
||||
|
||||
title: Install Appium
|
||||
title: 安装Appium
|
||||
---
|
||||
|
||||
!!! info
|
||||
!!! 信息
|
||||
|
||||
```
|
||||
Before installing, make sure to check the [System Requirements](./requirements.md).
|
||||
安装前,请确保检查 [系统要求] (./requirements.md)。
|
||||
```
|
||||
|
||||
Appium can be installed globally using `npm`:
|
||||
Appium 可以使用 "npm" 在全局安装:
|
||||
|
||||
```bash
|
||||
npm install -g appium
|
||||
```
|
||||
|
||||
!!! note
|
||||
!!! 备注
|
||||
|
||||
```
|
||||
Other package managers are not currently supported.
|
||||
目前不支持其他软件包管理。
|
||||
```
|
||||
|
||||
## Starting Appium
|
||||
## 启动Appium
|
||||
|
||||
Appium can be started [using the command line](../reference/cli/index.md):
|
||||
Appium 可以使用 [命令行](../reference/cli/index.md) 启动:
|
||||
|
||||
```
|
||||
appium
|
||||
```
|
||||
|
||||
This launches the Appium server process, which loads all the installed Appium drivers, and
|
||||
begins waiting for new session requests from client connections (such as test automation scripts).
|
||||
Since the server process is independent from its clients, it must be explicitly launched before
|
||||
attempting to start a new session.
|
||||
这会启动Appium服务器进程,该进程加载所有已安装的Appium驱动程序,并开始等待来自客户端连接(如测试自动化脚本)的新会话请求。
|
||||
由于服务器进程独立于其客户端,因此必须在尝试启动新会话之前明确启动它。
|
||||
|
||||
When the server is launched, the console log will list all the valid URLs that clients can use to
|
||||
connect to this server:
|
||||
当服务器启动时,控制台日志将列出客户端可以用来连接到此服务器的所有有效URL:
|
||||
|
||||
```
|
||||
[Appium] You can provide the following URLs in your client code to connect to this server:
|
||||
@@ -45,10 +42,6 @@ connect to this server:
|
||||
(... any other URLs ...)
|
||||
```
|
||||
|
||||
Once a client requests a new session, the Appium server process will start logging all details about
|
||||
this session until its termination. Keep this in mind - if you ever encounter issues with Appium
|
||||
tests, you can always check the server log for more details.
|
||||
一旦客户端请求新会话,Appium服务器进程将开始记录此会话的所有详细信息,直到其终止。 请记住这一点——如果您遇到Appium测试的问题,您可以随时检查服务器日志以获取更多详细信息。
|
||||
|
||||
So what's next? Even though Appium is installed and running, it does not come bundled with any
|
||||
drivers, which means it cannot automate anything yet. We will therefore set up automation for
|
||||
Android - continue to [Installing the UiAutomator2 Driver](./uiauto2-driver.md).
|
||||
接下来是什么? 即使Appium已安装并运行,它也不捆绑任何驱动程序,这意味着它还不能自动化任何东西。 因此,我们将为Android设置自动化——继续[安装UiAutomator2驱动程序](./uiauto2-driver.md)。
|
||||
|
||||
@@ -2,22 +2,18 @@
|
||||
hide:
|
||||
- toc
|
||||
|
||||
title: Next Steps
|
||||
title: 下一步
|
||||
---
|
||||
|
||||
Now that you've successfully set up your system for Android automation and run a simple test,
|
||||
you'll want to continue exploring this documentation. In particular, these are good guides and
|
||||
reference materials especially for beginners:
|
||||
现在您已成功为Android自动化设置了系统并运行了一个简单的测试,您将希望继续探索此文档。 特别是,这些是适合初学者的优秀指南和参考资料: 特别是,这些是适合初学者的优秀指南和参考资料:
|
||||
|
||||
- The [Ecosystem](../ecosystem/index.md) page: browse the available drivers, clients, plugins, and tools
|
||||
- [Managing Appium Drivers and Plugins](../guides/managing-exts.md)
|
||||
- [Capabilities](../guides/caps.md)
|
||||
- [Settings](../guides/settings.md)
|
||||
- [生态系统](../ecosystem/index.md) 页面:浏览可用的驱动程序、客户端、插件和工具
|
||||
- [管理Appium驱动程序和插件](../guides/managing-exts.md)
|
||||
- [功能](../guides/caps.md)
|
||||
- [设置](../guides/settings.md)
|
||||
|
||||
You'll also find that the [Appium Inspector](https://github.com/appium/appium-inspector) is an
|
||||
indispensable tool for writing Appium tests, as it enables visual inspection of apps and
|
||||
helps you to discover element locators for use in your test scripts.
|
||||
您还会发现[Appium Inspector](https://github.com/appium/appium-inspector)是编写Appium测试不可或缺的工具,因为它允许对应用进行视觉检查,并帮助您发现测试脚本中使用的元素定位器。
|
||||
|
||||
You might also take advantage of one of the many online Appium courses available to you.
|
||||
您还可以利用众多可用的在线Appium课程之一。
|
||||
|
||||
Good luck and have fun!
|
||||
祝您好运,玩得开心!
|
||||
|
||||
@@ -2,28 +2,20 @@
|
||||
hide:
|
||||
- toc
|
||||
|
||||
title: System Requirements
|
||||
title: 系统要求
|
||||
---
|
||||
|
||||
The basic requirements for the Appium server are:
|
||||
Appium 服务器的基本要求如下:
|
||||
|
||||
- A macOS, Linux, or Windows operating system
|
||||
- [Node.js](https://nodejs.org) version in the [SemVer](https://semver.org) range `^20.19.0 || ^22.12.0 || >=24.0.0`
|
||||
- LTS is recommended
|
||||
- [`npm`](https://npmjs.com) version `>=10` (`npm` is usually bundled with Node.js, but can be upgraded
|
||||
independently)
|
||||
- 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 捆绑,但可以独立升级)
|
||||
|
||||
By itself, Appium is relatively lightweight and doesn't have significant disk space or RAM
|
||||
requirements. It can even be run in resource-constrained environments like Raspberry Pi, so long as
|
||||
Node.js is available.
|
||||
Appium 本身相对轻量,没有显著的磁盘空间或 RAM 要求。 即使在资源受限的环境如 Raspberry Pi 中,只要有 Node.js 就可以运行。
|
||||
|
||||
### Driver Requirements
|
||||
### 驱动程序要求
|
||||
|
||||
Drivers for automating specific platforms will likely have other requirements. Refer to the
|
||||
documentation of the [Appium driver(s)](../ecosystem/drivers.md) for that platform for additional
|
||||
dependencies. It is almost universally the case that Appium drivers for a given platform will
|
||||
require the developer toolchain and SDKs for that platform to be installed.
|
||||
用于自动化特定平台的驱动程序可能有其他要求。 请参考该平台的 [Appium 驱动程序](../ecosystem/drivers.md) 文档以获取其他依赖项。 普遍的情况是,给定平台的 Appium 驱动程序需要安装该平台的开发者工具链和 SDK。
|
||||
|
||||
In order to assist with driver requirements, each (official) driver comes with the Appium Doctor tool,
|
||||
which allows to verify if all requirements have been set up. Learn more about how to use this tool in
|
||||
the [Command-Line Usage documentation](../reference/cli/extensions.md#doctor).
|
||||
为了帮助处理驱动程序要求,每个(官方)驱动程序都附带 Appium Doctor 工具,它允许验证是否已设置所有要求。 了解如何使用此工具的更多信息,请参阅 [命令行使用文档](../reference/cli/extensions.md#doctor)。
|
||||
|
||||
@@ -2,13 +2,13 @@
|
||||
hide:
|
||||
- toc
|
||||
|
||||
title: Write a Test (.NET)
|
||||
title: 编写测试 (.NET)
|
||||
---
|
||||
|
||||
The [Appium .NET Client](https://github.com/appium/dotnet-client/) is
|
||||
an official Appium client in C#. This driver is an extension of the Selenium C# client. It has all the functionalities of the regular driver, but add Appium-specific methods on top of this. The driver is available on the public NuGet Gallery as [Appium.WebDriver](https://www.nuget.org/packages/Appium.WebDriver/).
|
||||
[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/) 提供。
|
||||
|
||||
Now, we get inside the directory and create a new [NUnit](https://nunit.org/) project. We will also add the references to the Appium.Net driver, and other dependencies.
|
||||
现在,我们进入目录并创建一个新的 [NUnit](https://nunit.org/) 项目。 我们还将添加对 Appium.Net 驱动程序和其他依赖项的引用。
|
||||
|
||||
```bash
|
||||
cd dotnet-client
|
||||
@@ -16,12 +16,12 @@ dotnet new nunit --name appiumtest
|
||||
|
||||
cd appiumtest
|
||||
|
||||
# This will install the latest 5.x version
|
||||
# 这将安装最新的 5.x 版本
|
||||
dotnet add package Appium.WebDriver --prerelease
|
||||
dotnet add package Newtonsoft.Json --version 13.0.3
|
||||
```
|
||||
|
||||
Once this is done, your project should have a placeholder file `UnitTest1.cs`. We will replace the code to include the OpenQA namespaces, an initialization of the driver, and the actual test.
|
||||
完成后,您的项目应该有一个占位符文件 `UnitTest1.cs`。 我们将替换代码以包含 OpenQA 命名空间、驱动程序的初始化以及实际测试。
|
||||
|
||||
```C# title="UnitTest1.cs"
|
||||
using OpenQA.Selenium;
|
||||
@@ -69,39 +69,31 @@ public class Tests
|
||||
}
|
||||
```
|
||||
|
||||
!!! note
|
||||
!!! 备注
|
||||
|
||||
```
|
||||
It's not within the scope of this guide to give a complete run-down on the dotnet client
|
||||
library or everything that's happening here, so we'll leave the code itself unexplained in
|
||||
detail for now. You may want to read up particularly on Appium
|
||||
[Capabilities](../guides/caps.md) in addition to familiarizing yourself with the
|
||||
[dotnet client driver documentation](https://github.com/appium/dotnet-client/) for a fuller explanation
|
||||
of the various API commands you see and what their purpose is.
|
||||
这份指南的范围不包括对 dotnet 客户端库或此处发生的一切进行完整说明,因此我们暂时不对代码本身进行详细解释。您可能需要特别阅读 Appium [Capabilities](../guides/caps.md),以及熟悉 [dotnet 客户端驱动程序文档](https://github.com/appium/dotnet-client/) 以获得对您看到的各种 API 命令及其目的的更全面解释。
|
||||
```
|
||||
|
||||
Basically, this code is doing the following:
|
||||
基本上,此代码执行以下操作:
|
||||
|
||||
1. Defining a set of "Capabilities" (parameters) to send to the Appium server so Appium knows what
|
||||
kind of thing you want to automate. Some of these parameters can be overridden using environment variables.
|
||||
2. Starting an Appium session on the built-in Android settings app.
|
||||
3. Finding the "Apps" list item and clicking it.
|
||||
4. Ending the Appium session.
|
||||
1. 定义一组"Capabilities"(参数)发送到 Appium 服务器,以便 Appium 知道您想要自动化什么。 有些参数可以使用环境变量覆盖。
|
||||
2. 在内置的 Android 设置应用上启动 Appium 会话。
|
||||
3. 查找"Apps"列表项并点击它。
|
||||
4. 结束 Appium 会话。
|
||||
|
||||
That's it! Let's give it a try. Before you run the test, make sure that you have an Appium server
|
||||
running in another terminal session, otherwise you'll get an error about not being able to connect
|
||||
to one. Then, you can execute the script:
|
||||
就是这样! 让我们试试。 在运行测试之前,请确保在另一个终端会话中运行 Appium 服务器,否则您会收到无法连接的错误。 然后,您可以执行脚本:
|
||||
|
||||
```bash
|
||||
dotnet test
|
||||
|
||||
# Example output:
|
||||
# 示例输出:
|
||||
# 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)
|
||||
```
|
||||
|
||||
If all goes well, you'll see the Settings app open up and navigate to the "Apps" view in the emulator before the app closes again.
|
||||
如果一切顺利,您将看到设置应用打开并在模拟器中导航到"Apps"视图,然后应用再次关闭。
|
||||
|
||||
Congratulations, you've started your Appium journey! Read on for some [next steps](./next-steps.md) to explore.
|
||||
恭喜,您已经开始了 Appium 之旅! 继续阅读一些 [后续步骤](./next-steps.md) 以进行探索。
|
||||
|
||||
Reference in New Issue
Block a user