@appium/mcp-documentation 1.0.2 → 1.0.4

package/src/resources/submodules/appium/packages/appium/docs/en/reference/cli/env-vars.md

@@ -0,0 +1,31 @@
+---
+hide:
+  - toc
+
+title: Environment Variables
+---
+
+The primary ways of configuring the Appium server are via [Command-Line Arguments](./server.md) or
+the [Config File](../../guides/config.md). However, some more advanced features are toggled or
+configured via environment variables. To set environment variables, refer to the documentation for
+your operating system and terminal.
+
+These are the environment variables that the Appium server understands:
+
+|<div style="width:18em">Variable</div>|Description|
+|--------|-----------|
+|`APPIUM_APPS_CACHE_IGNORE_URL_QUERY`|Set this to a truthy value to remove any query part of a URL when using it as a cache key. See the corresponding [feature request](https://discuss.appium.io/t/regarding-app-caching-when-using-aws-s3-presigned-urls/42713) for more details.|
+|`APPIUM_APPS_CACHE_MAX_AGE`|Set the maximum age (in minutes) for [cached applications](../../guides/caching.md). Do not set it to a lower number than the duration of a single session startup. Default: `60 * 24` (24 hours)|
+|`APPIUM_APPS_CACHE_MAX_ITEMS`|Set the maximum amount of [cached applications](../../guides/caching.md). Do not set it to a lower number than the amount of apps in all parallel sessions per process. Default: `1024`|
+|`APPIUM_HOME`|Set the path to the Appium home directory, which is used for [Managing Extensions](../../guides/managing-exts.md). Default: `.appium` in the home directory of the current user|
+|`APPIUM_OMIT_PEER_DEPS`|Set this to `1` to add `--omit=peer` to all the NPM commands run internally by Appium. Mostly an internal feature.|
+|`APPIUM_RELOAD_EXTENSIONS`|Set this to a truthy value to cause Appium to re-require extensions when new sessions are created. This feature is mostly useful for [building extensions](../../developing/build-drivers.md).|
+|`APPIUM_TMP_DIR`|Set the path to the directory used for temporary files. Same as the `--tmp` command line argument.|
+
+Appium drivers and plugins may define additional environment variables. The following variables are
+used by official plugins:
+
+|<div style="width:13em">Variable</div>|Plugin|Description|
+|--------|-----------|-----------|
+|`APPIUM_STORAGE_KEEP_ALL`|`storage`|Set this to `1`, `true` or `yes` to preserve files in the storage after the server process is terminated. By default, stopping the server process also deletes all files in the storage.|
+|`APPIUM_STORAGE_ROOT`|`storage`|Set the path to the directory used for storage. If set to an existing folder, all files in it will be retained after terminating the server, unless specified otherwise using `APPIUM_STORAGE_KEEP_ALL`.|

package/src/resources/submodules/appium/packages/appium/docs/en/reference/cli/extensions.md

@@ -0,0 +1,246 @@
+---
+title: appium driver/plugin
+---
+<style>
+  ul[data-md-component="toc"] .md-nav {
+    display: none;
+  }
+</style>
+
+Provides management options for a specific extension (driver or plugin). Both the `appium driver` and
+`appium plugin` subcommands support the same options.
+
+The following sub-subcommands are supported: `doctor`, `install`, `list`, `run`, `update`,
+and `uninstall`.
+
+## `doctor`
+
+Runs doctor checks for an installed extension, which validate whether the extension has its prerequisites
+configured correctly. Note that not all extensions include doctor checks.
+
+!!! note
+
+    If you maintain an Appium extension and would like to add Appium Doctor support for it, check
+    out the documentation on [Building Doctor Checks](../../developing/build-doctor-checks.md).
+
+#### Usage
+
+```
+appium {driver|plugin} doctor <extension-name>
+```
+
+|Argument|Description|
+|--|--|
+|`extension-name`|The short name of the installed extension|
+
+#### Options
+
+|Argument|Description|Type|
+|--|--|--|
+|`--json`|Return the result in JSON format|boolean|
+
+#### Example
+
+- Run doctor checks for the UiAutomator2 driver:
+
+    ```
+    appium driver doctor uiautomator2
+    ```
+
+## `install`
+
+Installs an extension.
+
+#### Usage
+
+```
+appium {driver|plugin} install <install-spec>
+```
+
+|<div style="width:7em">Argument</div>|Description|
+|--|--|
+|`install-spec`|The short name of an official extension, with optional `npm` version or tag modifier. If using the `--source` option, the expected format of this argument will change ([see below](#source-vs-install-spec)).|
+
+#### Options
+
+|Argument|Description|Type|
+|--|--|--|
+|`--json`|Return the result in JSON format|boolean|
+|`--package`|The Node.js package name of the extension. Required if `--source` is set to `git` or `github`.|string|
+|`--source`|The location where Appium should look for the given extension. Supported values are `git`, `github`, `local`, or `npm`. Changes the expected format of `install-spec` ([see below](#source-vs-install-spec)).|string|
+
+#### Source vs Install Spec
+
+|`source`|Format of `<install-spec>`|
+|--|--|
+|None|The short name of an official extension, with optional modifiers as supported by `npm install` (e.g. version or tag)|
+|`git`|The Git URL of the extension|
+|`github`|The GitHub repository URL of the extension|
+|`local`|The local path to the extension containing its `package.json` file|
+|`npm`|The name of the `npm` package, with optional modifiers as supported by `npm install` (e.g. version or tag)|
+
+#### Examples
+
+- Install the latest XCUITest driver:
+
+    ```
+    appium driver install xcuitest
+    ```
+
+- Install the XCUITest driver at version 9.0.0:
+
+    ```
+    appium driver install xcuitest@9.0.0
+    ```
+
+- Install the `beta` version of `@appium/fake-driver` from `npm`:
+
+    ```
+    appium driver install @appium/fake-driver@beta --source=npm
+    ```
+
+- Install a locally-developed plugin:
+
+    ```
+    appium plugin install /path/to/my/plugin --source=local
+    ```
+
+- Install the XCUITest driver from GitHub:
+
+    ```
+    appium driver install https://github.com/appium/appium-xcuitest-driver --source=github --package=appium-xcuitest-driver
+    ```
+
+- Install the XCUITest driver using a Git URL:
+
+    ```
+    appium driver install git://github.com/appium/appium-xcuitest-driver.git --source=git --package=appium-xcuitest-driver
+    ```
+
+- Install a branch of XCUITest driver repository using a Git URL:
+
+    ```
+    appium driver install git://github.com/appium/appium-xcuitest-driver.git#specific-branch --source=git --package=appium-xcuitest-driver
+    ```
+
+## `list`
+
+Lists all installed extensions, plus all official extensions that are not installed.
+
+#### Usage
+
+```
+appium {driver|plugin} list
+```
+
+#### Options
+
+|<div style="width:7em">Argument</div>|Description|Type|
+|--|--|--|
+|`--installed`|Only list all installed extensions|boolean|
+|`--json`|Return the result in JSON format|boolean|
+|`--updates`|List all extensions along with information on whether newer versions are available. Only supported for extensions installed via `npm`.|boolean|
+|`--verbose`|Show additional details for each extension|boolean|
+
+#### Example
+
+- List all installed drivers and check if they have newer versions available:
+
+    ```
+    appium driver list --installed --updates
+    ```
+
+## `run`
+
+Runs an extension script, which can assist with setup or perform other tasks. Note that not all
+extensions include scripts.
+
+#### Usage
+
+```
+appium {driver|plugin} run <extension-name> <script-name> [script-args]
+```
+
+|Argument|Description|
+|--|--|
+|`extension-name`|The short name of the installed extension|
+|`script-name`|The name of the script to be run|
+|`script-args`|Any additional arguments passed to the script|
+
+#### Options
+
+|Argument|Description|Type|
+|--|--|--|
+|`--json`|Return the result in JSON format|boolean|
+
+#### Example
+
+- Run the `reset` script included in the UiAutomator2 driver:
+
+    ```
+    appium driver run uiautomator2 reset
+    ```
+
+## `update`
+
+Updates one or more extensions. Only supported for extensions installed via `npm`. By default,
+Appium will only update minor and patch versions, in order to prevent any breaking changes.
+
+#### Usage
+
+```
+appium {driver|plugin} update <extension-name>
+```
+
+|Argument|Description|
+|--|--|
+|`extension-name`|The short name of the installed extension, or `installed` to update all installed extensions|
+
+#### Options
+
+|Argument|Description|Type|
+|--|--|--|
+|`--json`|Return the result in JSON format|boolean|
+|`--unsafe`|Allow updates of major versions, which may cause breaking changes|boolean|
+
+#### Examples
+
+- Update the UiAutomator2 driver to its latest major version:
+
+    ```
+    appium driver update uiautomator2 --unsafe
+    ```
+
+- Update all installed plugins:
+
+    ```
+    appium plugin update installed
+    ```
+
+## `uninstall`
+
+Removes an installed extension.
+
+#### Usage
+
+```
+appium {driver|plugin} uninstall <extension-name>
+```
+
+|Argument|Description|
+|--|--|
+|`extension-name`|The short name of the installed extension|
+
+#### Options
+
+|Argument|Description|Type|
+|--|--|--|
+|`--json`|Return the result in JSON format|boolean|
+
+#### Example
+
+- Remove the `images` plugin:
+
+    ```
+    appium plugin uninstall images
+    ```

package/src/resources/submodules/appium/packages/appium/docs/en/reference/cli/index.md

@@ -0,0 +1,36 @@
+---
+hide:
+  - toc
+
+title: Command Line Interface
+---
+
+Appium provides a command-line executable (`appium`), which can be used to configure and launch
+the Appium server, as well as manage Appium extensions (drivers and plugins).
+
+The executable has four main subcommands: `server`, `driver`, `plugin`, and `setup`. All subcommands
+(and sub-subcommands) can be run with the `--help`/`-h` option for usage instructions.
+
+<div class="grid cards" markdown>
+
+-   [__`appium server`__](./server.md) (or simply `appium`)
+
+    Start an Appium server
+
+-   [__`appium driver`__](./extensions.md)
+
+    Manage individual drivers
+
+-   [__`appium plugin`__](./extensions.md)
+
+    Manage individual plugins
+
+-   [__`appium setup`__](./setup.md)
+
+    Manage multiple drivers/plugins
+
+</div>
+
+The Appium server also recognizes several [environment variables](./env-vars.md) and
+[insecure feature names](./insecure-features.md), though drivers and plugins can also define
+variables and features of their own.

package/src/resources/submodules/appium/packages/appium/docs/en/reference/cli/insecure-features.md

@@ -0,0 +1,24 @@
+---
+hide:
+  - toc
+
+title: Insecure Features
+---
+
+The Appium server implements [a security protection mechanism](../../guides/security.md) that
+allows the management of various insecure features.
+
+The following features are defined on the server level and can be used even without drivers, but
+they can only be enabled using the wildcard (`*`) prefix:
+
+| Feature Name      | Description                                                                   |
+|-------------------|-------------------------------------------------------------------------------|
+|`session_discovery`|Allows retrieving the list of active server sessions via `GET /appium/sessions`|
+
+
+Of course, Appium drivers and plugins are free to define additional insecure features of their own.
+The following features are defined by official plugins:
+
+| Feature Name          | Plugin         | Description                                              |
+|-----------------------|----------------|----------------------------------------------------------|
+|`execute_driver_script`|`execute_driver`|Allows sending a request that has multiple Appium commands|

package/src/resources/submodules/appium/packages/appium/docs/en/reference/cli/server.md

@@ -0,0 +1,78 @@
+---
+hide:
+  - toc
+
+title: appium server
+---
+
+Launches an Appium server.
+
+```
+appium server
+```
+
+You can also omit the `server` subcommand:
+
+```
+appium
+```
+
+### Options
+
+!!! note
+
+    All of these options can also be set via a [Configuration File](../../guides/config.md). Options
+    set on the command line will override any options found in a configuration file.
+
+|<div style="width:15em">Argument</div>|Description|Type|<div style="width:7em">Default</div>|
+|--|--|--|--|
+|`--address`, `-a`|IPv4/IPv6 address to listen on|string|`0.0.0.0`|
+|`--allow-cors`|Allow web browser connections from any host|boolean|`false`|
+|`--allow-insecure`|List of [insecure features](../../guides/security.md) that should be allowed in this server's sessions. Individual features can be overridden by `--deny-insecure`. Has no effect in combination with `--relaxed-security`.|array<string>|`[]`|
+|`--base-path`, `-pa`|Base path to use as the prefix for all webdriver routes running on the server|string|`""`|
+|`--callback-address`, `-ca`|Callback IP address|string|`0.0.0.0`|
+|`--callback-port`, `-cp`|Callback port|integer|`4723`|
+|`--config`|Path to an [Appium configuration JSON file](../../guides/config.md)|string||
+|`--debug-log-spacing`|Add exaggerated spacing in logs to help with visual inspection|boolean|`false`|
+|`--default-capabilities`, `-dc`|Capabilities that will be used for each session, unless overridden by received capabilities|object||
+|`--deny-insecure`|List of [insecure features](../../guides/security.md) that should be disabled in this server's sessions. Since all insecure features are disabled by default, this argument has no effect without either `--allow-insecure` or `--relaxed-security`, and is applied after both.|array<string>|`[]`|
+|`--driver`|Driver-specific configuration. Keys should correspond to driver package names|object||
+|`--drivers-import-chunk-size`|Maximum number of drivers that can be imported in parallel on server startup|number|`3`|
+|`--keep-alive-timeout`, `-ka`|Timeout (in seconds) to use as both the keep-alive timeout and the connection timeout for all client requests. Disabled if set to `0`.|integer|`600`|
+|`--request-timeout`|Timeout (in seconds) for waiting to receive the entire HTTP request from the client. Disabled if set to `0`. Requests exceeding this timeout will be rejected with the code `HTTP 408`.|integer|`3600`|
+|`--local-timezone`|Use local timezone for log timestamps|boolean|`false`|
+|`--log`, `-g`|Path to a file where the server logs should be output. This does not affect output on the console.|string||
+|`--log-filters`|List of log filtering rules. See the [log filtering guide](../../guides/log-filters.md) for details.|array||
+|`--log-level`|The log level for the server logs. Supported values are `debug`, `info`, `warn`, or `error`. Combining two supported values using a colon (e.g. `warn:debug`) allows to set separate log levels for the console and file outputs, respectively.|string|`debug`|
+|`--log-format`|The log format of the server logs. Supported values are `text`, `json`, or `pretty_json`. Setting the value to `json` disables colors.|string|`text`|
+|`--log-no-colors`|Disable colors in the server log|boolean|`false`|
+|`--log-timestamp`|Show timestamps in the server log|boolean|`false`|
+|`--long-stacktrace`|Add long stack traces to log entries. Recommended for debugging only.|boolean|`false`|
+|`--max-ipc-data-size`|Maximum byte size of IPC message objects.|integer|`1048576` (1MB)|
+|`--max-ipc-topics`|Maximum number of IPC topics per session.|integer|`1000`|
+|`--no-perms-check`|Skip various permission checks on the server startup|boolean|`false`|
+|`--nodeconfig`|JSON configuration for registering Appium as a node with Selenium Grid 3|object||
+|`--plugin`|Plugin-specific configuration. Keys should correspond to plugin package names|object||
+|`--plugins-import-chunk-size`|Maximum number of plugins that can be imported in parallel on server startup|number|`7`|
+|`--port`, `-p`|Port to listen on|integer|`4723`|
+|`--relaxed-security`|Allow all [insecure features](../../guides/security.md). Only use this if all clients are in a trusted network and could not potentially break out of the session sandbox. Specific features can be overridden by using `--deny-insecure`.|boolean|`false`|
+|`--session-override`|Enable session override (clobbering)|boolean|`false`|
+|`--shutdown-timeout`|Timeout (in milliseconds) for waiting on all active connections to close, when shutting down the server|number|`5000`|
+|`--ssl-cert-path`|Absolute path to the `.cert` file if TLS is used. Must be provided together with `--ssl-key-path`. See the [SSL/TLS/SPDY Support guide](../../guides/tls.md) for details.|string||
+|`--ssl-key-path`|Absolute path to the `.key` file if TLS is used. Must be provided together with `--ssl-cert-path`. See the [SSL/TLS/SPDY Support guide](../../guides/tls.md) for details.|string||
+|`--strict-caps`|Prevent creation of new client sessions that use unsupported capabilities|boolean|`false`|
+|`--tmp`|Absolute path to the directory used for temporary files|string|[`os.tmpdir()`](https://nodejs.org/api/os.html#ostmpdir)|
+|`--use-drivers`|List of drivers to activate. By default, all installed drivers are activated.|array<string>|`[]`|
+|`--use-plugins`|List of plugins to activate. By default, no plugins are activated. Set to `["all"]` to activate all installed plugins.|array<string>|`[]`|
+|`--webhook`, `-G`|URL for an HTTP listener where the server logs should be output. This does not affect output on the console.|string||
+
+### Info Options
+
+The following options are used for reference or debug purposes. They are only supported for the base `appium` command (not `appium server`), and will not launch the server.
+
+|<div style="width:10em">Argument</div>|Description|
+|--|--|
+|`--show-build-info`|Print detailed information on the Appium server version|
+|`--show-config`|Print the current Appium server configuration details|
+|`--show-debug-info`|Print information on the current environment: details about the operating system, Node.js, and Appium itself|
+|`--version`, `-v`|Print the Appium server version|

package/src/resources/submodules/appium/packages/appium/docs/en/reference/cli/setup.md

@@ -0,0 +1,76 @@
+---
+title: appium setup
+---
+<style>
+  ul[data-md-component="toc"] .md-nav {
+    display: none;
+  }
+</style>
+
+Installs a specific preset of extensions (drivers and plugins), or uninstalls all extensions.
+When installing a preset, any already installed extensions are kept intact.
+
+The following sub-subcommands are supported: `browser`, `desktop`, `mobile`, and `reset`.
+
+Refer to the [Ecosystem documentation](../../ecosystem/index.md) to learn more about the extensions
+mentioned below.
+
+## `browser`
+
+Installs the following extensions for browser webview testing:
+
+* Drivers: `safari`[^1], `gecko`, `chromium`
+* Plugins: `images`, `inspector`
+
+#### Usage
+
+```
+appium setup browser
+```
+
+## `desktop`
+
+Installs the following extensions for desktop application testing:
+
+* Drivers: `mac2`[^1], `windows`[^2]
+* Plugins: `images`, `inspector`
+
+#### Usage
+
+```
+appium setup desktop
+```
+
+## `mobile`
+
+Installs the following extensions for mobile testing:
+
+* Drivers: `uiautomator2`, `xcuitest`[^1], `espresso`
+* Plugins: `images`, `inspector`
+
+#### Usage
+
+```
+appium setup mobile
+```
+
+You can also omit the `mobile` sub-subcommand:
+
+```
+appium setup
+```
+
+## `reset`
+
+Uninstalls all installed extensions, along with their manifest files, from the Appium home
+directory. This can be useful if you experience configuration issues on server startup, for
+example, due to a failed upgrade attempt from an older Appium version.
+
+#### Usage
+
+```
+appium setup reset
+```
+
+[^1]: Only installed if the host machine is running macOS.
+[^2]: Only installed if the host machine is running Windows.

package/src/resources/submodules/appium/packages/appium/docs/en/reference/index.md

@@ -0,0 +1,31 @@
+---
+hide:
+  - toc
+
+title: Reference
+---
+
+This section of the Appium documentation provides a reference to the core interfaces supported within the
+Appium server:
+
+<div class="grid cards" markdown>
+
+-   :octicons-command-palette-16: [__Command Line Interface__](./cli/index.md)
+
+    ---
+
+    Learn how to use the Appium command-line executable
+
+-   :material-lan-connect: [__Session Properties__](./session/index.md)
+
+    ---
+
+    See the values of global Appium session properties 
+
+-   :material-cloud-braces: [__API Endpoints__](./api/index.md)
+
+    ---
+
+    View endpoints supported by the core Appium server
+
+</div>

package/src/resources/submodules/appium/packages/appium/docs/en/reference/session/caps.md

@@ -0,0 +1,56 @@
+---
+hide:
+  - toc
+
+title: Capabilities
+---
+
+The following [capabilities](../../guides/caps.md) are recognized by the Appium server/base driver,
+and are therefore supported by all drivers as well. Some capabilities are directly handled by the
+server/base driver, while others are only validated before being passed to the actual driver.
+
+!!! note
+
+    Capabilities not listed here will _not_ be rejected by Appium: they will simply be forwarded
+    directly to the active driver/plugin.
+
+### Required Capabilities
+
+These capabilities are used in the Appium server/base driver, and are explicitly required in all
+Appium sessions.
+
+| Capability              | Description                                 | Type      |
+|-------------------------|---------------------------------------------|-----------|
+| `platformName`          | Type of platform hosting the app or browser | `string`  |
+| `appium:automationName` | Name of the Appium driver to use            | `string`  |
+
+### Optional Capabilities
+
+These capabilities are used in the Appium server/base driver, but are optional, and may have a
+default value.
+
+| <div style="width:19em">Capability</div> | Description | Type | Default |
+|--|--|--|--|
+| `webSocketUrl` | Toggle support of the WebDriver BiDi protocol | `boolean` ||
+| `appium:eventTimings` (deprecated) | Toggle collection of [Event Timings](../../guides/event-timing.md). This capability is deprecated - please use the [`getLogEvents`](../api/appium.md#getlogevents) endpoint instead. | `boolean` ||
+| `appium:newCommandTimeout` | Number of seconds the Appium server should wait for clients to send commands before stopping the session. A value of `0` disables the timeout. | `number` | `60` |
+| `appium:printPageSourceOnFindFailure` | Toggle retrieval of the the page source and its printing to the Appium log, whenever a request to find an element fails | `boolean` ||
+
+### Validated Capabilities
+
+These capabilities are not directly used in the Appium server/base driver, but are still subject to
+validation checks due to their relevance in other drivers. The actual handling of these
+capabilities is optional and entirely driver-dependent.
+
+| Capability                        | Validation                                                    |
+|-----------------------------------|---------------------------------------------------------------|
+| `platformVersion`                 | Must be `string`                                              |
+| `appium:app`                      | Must be `string`; empty values are ignored                    |
+| `appium:autoLaunch` (deprecated)  | Must be `boolean`                                             |
+| `appium:autoWebview`              | Must be `boolean`                                             |
+| `appium:fullReset`                | Must be `boolean`; mutually exclusive with `appium:noReset`   |
+| `appium:language`                 | Must be `string`                                              |
+| `appium:locale`                   | Must be `string`                                              |
+| `appium:orientation`              | Must be either `LANDSCAPE` or `PORTRAIT`                      |
+| `appium:noReset`                  | Must be `boolean`; mutually exclusive with `appium:fullReset` |
+| `appium:udid`                     | Must be `string`                                              |

package/src/resources/submodules/appium/packages/appium/docs/en/reference/session/index.md

@@ -0,0 +1,23 @@
+---
+hide:
+  - toc
+
+title: Session Properties
+---
+
+An Appium session has several key properties, each with its own set of supported values:
+capabilities, execute methods, settings, locator strategies, and others. The supported values for
+each property are primarily defined by the active driver and plugins, but some properties also have
+common values provided by the Appium server and its base driver:
+
+<div class="grid cards" markdown>
+
+-   [__Capabilities__](./caps.md)
+
+    A small set of basic capabilities
+
+-   [__Command Endpoints__](../api/index.md)
+
+    The core set of API endpoints
+
+</div>

package/src/resources/submodules/appium/packages/appium/docs/en/resources/index.md

@@ -0,0 +1,28 @@
+---
+hide:
+  - navigation
+  - toc
+
+title: Additional Resources
+---
+
+Here you can find links to additional Appium resources around the web:
+
+## Websites
+
+- [Appium Pro](https://appiumpro.com) - a blog and newsletter written by one of Appium's
+maintainers, Jonathan Lipps, with lots of useful guides
+
+## Online Courses
+
+- [Appium and Selenium Fundamentals](https://ui.headspin.io/university/learn/appium-selenium-fundamentals-2020) - a comprehensive video course on learning Python, Selenium, and Appium by Jonathan Lipps
+- [Mobile Test Automation with Appium](https://testautomationu.applitools.com/appium-java-tutorial/) - a video course by Moataz Nabil
+- [Advanced Appium](https://www.linkedin.com/learning/advanced-appium) - a video course by Jonathan Lipps
+
+## Conference Archives
+
+- [AppiumConf 2018](https://www.youtube.com/playlist?list=PLhr2WKNPXcZOmOf1k2aqkbMZwnZb2pSZL)
+- [AppiumConf 2019](https://www.youtube.com/playlist?list=PL9Z-JgiTsOYSfJh9YKI9Stj3FMwHERw6w)
+- [AppiumConf 2021](https://www.youtube.com/playlist?list=PL9Z-JgiTsOYRCcJhDfmKAah9XmAp2b903)
+- [AppiumConf 2024](https://www.youtube.com/playlist?list=PL9Z-JgiTsOYQaU5i5LJtAWlh5WVZPi3If)
+- [SeleniumConf & AppiumConf 2025](https://www.youtube.com/playlist?list=PLRdSclUtJDYV2R92TLbmwxws6clruuTjH)