Skip to content

Commit 5c4e635

Browse files
Document changes in W3C vs JWP protocol selection
1 parent 8559d98 commit 5c4e635

File tree

1 file changed

+1
-7
lines changed

1 file changed

+1
-7
lines changed

docs/mobile-apps/automated-testing/appium/real-devices.md

Lines changed: 1 addition & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -54,13 +54,7 @@ The W3C WebDriver Protocol test capability syntax differs from that of JWP, so i
5454

5555
### How Sauce Labs Determines Your Protocol
5656

57-
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.
58-
59-
| Indicator | Determination |
60-
| :------------------------------------------------------------------------ | :------------ |
61-
| `sauce:options` node is present within the capabilities node. | W3C |
62-
| `desiredCapabilities` node is absent. | W3C |
63-
| `desiredCapabilities` node is present AND `sauce:options` node is absent. | JWP |
57+
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.
6458

6559
### Examples of JWP and W3C Configurations
6660

0 commit comments

Comments
 (0)