Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 1 addition & 7 deletions docs/mobile-apps/automated-testing/appium/real-devices.md
Original file line number Diff line number Diff line change
Expand Up @@ -54,13 +54,7 @@

### How Sauce Labs Determines Your Protocol

When Sauce Labs executes your test configuration, it looks for the presence of certain indicators in the session creation request to determine whether it should apply the JWP or W3C protocol. The following table outlines how Sauce Labs evaluates your creation request.

| Indicator | Determination |
| :------------------------------------------------------------------------ | :------------ |
| `sauce:options` node is present within the capabilities node. | W3C |
| `desiredCapabilities` node is absent. | W3C |
| `desiredCapabilities` node is present AND `sauce:options` node is absent. | JWP |
Sauce Labs always prioritizes W3C as the standard appium protocol. Most modern appium clients support sending both W3C and JWP in the session creation request. In this case, the W3C will be considered and the JWP ignored. The only scenario where JWP is used is when it is the only protocol available in the session creation request.

Check warning on line 57 in docs/mobile-apps/automated-testing/appium/real-devices.md

View workflow job for this annotation

GitHub Actions / vale

[vale] docs/mobile-apps/automated-testing/appium/real-devices.md#L57

[sauce.WordList] Use 'Appium' instead of 'appium'.
Raw output
{"message": "[sauce.WordList] Use 'Appium' instead of 'appium'.", "location": {"path": "docs/mobile-apps/automated-testing/appium/real-devices.md", "range": {"start": {"line": 57, "column": 51}}}, "severity": "WARNING"}

### Examples of JWP and W3C Configurations

Expand Down