mirror of
https://github.com/appium/appium.git
synced 2026-03-03 07:39:21 -06:00
docs(appium): Update documentation translations (#21488)
Co-authored-by: mykola-mokhnach <7767781+mykola-mokhnach@users.noreply.github.com>
This commit is contained in:
committed by
GitHub
parent
0761fd35c4
commit
fd5ac8d7a2
40
packages/appium/docs/ja/blog/posts/appium3.md
Normal file
40
packages/appium/docs/ja/blog/posts/appium3.md
Normal file
@@ -0,0 +1,40 @@
|
||||
---
|
||||
authors:
|
||||
- sai
|
||||
- srini
|
||||
- jlipps
|
||||
date: 2025-08-07
|
||||
---
|
||||
|
||||
# 🚀 Appium 3
|
||||
|
||||
Appium 3 is here — and while it's not as massive a leap as Appium 2, it introduces a few essential
|
||||
breaking changes that developers and QA engineers should be aware of.
|
||||
|
||||
<!-- more -->
|
||||
|
||||
The main idea behind Appium 3 is to clear out old cruft so that Appium can be leaner moving
|
||||
forward, and rely on newer versions of software with better performance and security
|
||||
characteristics. We're also getting rid of legacy behaviors and protocols that we deprecated as
|
||||
part of Appium 2.
|
||||
|
||||
For you as a user, there's not much to worry about. The breaking changes are minimal:
|
||||
|
||||
- Node.js / NPM minimum version bump (to 20.19 / 10)
|
||||
- Removal of certain deprecated endpoints
|
||||
- Security feature flag prefix requirements (e.g. `adb_shell` to `uiautomator2:adb_shell`)
|
||||
|
||||
In terms of new features, we've been adding them incrementally rather than saving them up for
|
||||
Appium 3. But with this release we are excited to share these new capabilities:
|
||||
|
||||
- `appium plugin install inspector` (Use Appium to host the Inspector rather than downloading it as a separate app)
|
||||
- Clients can set the `X-Appium-Is-Sensitive` HTTP header on requests to direct the server to mask the data in the request in the logs, so that when you send a password into an input box, the password's actual value is not logged in plaintext. ([Learn more](../../developing/sensitive.md))
|
||||
|
||||
Of course, we have a full [Appium 3 migration guide](../../guides/migrating-2-to-3.md) to make sure
|
||||
you know all the details and can deeply understand the consequences of upgrading to Appium 3 in
|
||||
your environment.
|
||||
|
||||
---
|
||||
|
||||
**Ready to make the leap?** Appium 3 is a great step forward in creating more secure, maintainable,
|
||||
and W3C-compliant test automation pipelines. Happy testing!
|
||||
@@ -13,6 +13,16 @@ title: Appium 3 へ移行する
|
||||
|
||||
Appium 2 はAppiumアーキテクチャ全体の大きな見直しをしました。 Appium 3 は限られた破壊的変更のみの比較的小さな更新であり、移行プロセスがはるかに簡易になります。
|
||||
|
||||
## Installation
|
||||
|
||||
The installation method for Appium 3 remains the same as for Appium 2. If you want to upgrade, you
|
||||
can simply install Appium 3 on top of your existing installation:
|
||||
|
||||
```bash
|
||||
# optional: `appium setup reset`
|
||||
npm install -g appium
|
||||
```
|
||||
|
||||
\## 破壊的変更
|
||||
|
||||
### Node 20+ Required
|
||||
|
||||
40
packages/appium/docs/zh/blog/posts/appium3.md
Normal file
40
packages/appium/docs/zh/blog/posts/appium3.md
Normal file
@@ -0,0 +1,40 @@
|
||||
---
|
||||
authors:
|
||||
- sai
|
||||
- srini
|
||||
- jlipps
|
||||
date: 2025-08-07
|
||||
---
|
||||
|
||||
# 🚀 Appium 3
|
||||
|
||||
Appium 3 is here — and while it's not as massive a leap as Appium 2, it introduces a few essential
|
||||
breaking changes that developers and QA engineers should be aware of.
|
||||
|
||||
<!-- more -->
|
||||
|
||||
The main idea behind Appium 3 is to clear out old cruft so that Appium can be leaner moving
|
||||
forward, and rely on newer versions of software with better performance and security
|
||||
characteristics. We're also getting rid of legacy behaviors and protocols that we deprecated as
|
||||
part of Appium 2.
|
||||
|
||||
For you as a user, there's not much to worry about. The breaking changes are minimal:
|
||||
|
||||
- Node.js / NPM minimum version bump (to 20.19 / 10)
|
||||
- Removal of certain deprecated endpoints
|
||||
- Security feature flag prefix requirements (e.g. `adb_shell` to `uiautomator2:adb_shell`)
|
||||
|
||||
In terms of new features, we've been adding them incrementally rather than saving them up for
|
||||
Appium 3. But with this release we are excited to share these new capabilities:
|
||||
|
||||
- `appium plugin install inspector` (Use Appium to host the Inspector rather than downloading it as a separate app)
|
||||
- Clients can set the `X-Appium-Is-Sensitive` HTTP header on requests to direct the server to mask the data in the request in the logs, so that when you send a password into an input box, the password's actual value is not logged in plaintext. ([Learn more](../../developing/sensitive.md))
|
||||
|
||||
Of course, we have a full [Appium 3 migration guide](../../guides/migrating-2-to-3.md) to make sure
|
||||
you know all the details and can deeply understand the consequences of upgrading to Appium 3 in
|
||||
your environment.
|
||||
|
||||
---
|
||||
|
||||
**Ready to make the leap?** Appium 3 is a great step forward in creating more secure, maintainable,
|
||||
and W3C-compliant test automation pipelines. Happy testing!
|
||||
@@ -14,6 +14,16 @@ It contains a list of breaking changes, as well as suggestions for handling them
|
||||
While Appium 2 was a major overhaul of the entire Appium architecture, Appium 3 is a smaller
|
||||
upgrade with fewer breaking changes, which should result in a much simpler migration process.
|
||||
|
||||
## Installation
|
||||
|
||||
The installation method for Appium 3 remains the same as for Appium 2. If you want to upgrade, you
|
||||
can simply install Appium 3 on top of your existing installation:
|
||||
|
||||
```bash
|
||||
# optional: `appium setup reset`
|
||||
npm install -g appium
|
||||
```
|
||||
|
||||
\## Breaking Changes
|
||||
|
||||
### Node 20+ Required
|
||||
|
||||
Reference in New Issue
Block a user