@wdio/types 9.0.0-alpha.9 → 9.0.0

package/build/Capabilities.d.ts

@@ -1,4 +1,4 @@
-import type { WebdriverIO as WebDriverIOOptions, Connection as ConnectionOptions } from './Options.js';
+import type { WebDriver as WebDriverOptions, WebdriverIO as WebDriverIOOptions, Connection as ConnectionOptions } from './Options.js';
 type JSONLike = {
     [property: string]: JSONLike;
 } | readonly JSONLike[] | string | number | boolean | null;
@@ -82,45 +82,178 @@ export interface W3CCapabilities {
     alwaysMatch: WebdriverIO.Capabilities;
     firstMatch: WebdriverIO.Capabilities[];
 }
-export type RemoteCapabilities = (DesiredCapabilities | W3CCapabilities)[] | MultiRemoteCapabilities | MultiRemoteCapabilities[];
-export interface MultiRemoteCapabilities {
-    [instanceName: string]: WebDriverIOOptions;
+export type RequestedStandaloneCapabilities = W3CCapabilities | WebdriverIO.Capabilities;
+export type RequestedMultiremoteCapabilities = {
+    [instanceName: string]: WebDriverIOOptions & WithRequestedCapabilities;
+};
+/**
+ * Configuration object for the `webdriver` package
+ */
+export type RemoteConfig = WebDriverOptions & WithRequestedCapabilities;
+/**
+ * Configuration object for the `webdriverio` package
+ */
+export type WebdriverIOConfig = WebDriverIOOptions & WithRequestedCapabilities;
+export type WebdriverIOMultiremoteConfig = WebDriverIOOptions & {
+    capabilities: RequestedMultiremoteCapabilities;
+};
+/**
+ * A type referencing all possible capability types when using Testrunner
+ * e.g. everything a user can provide in the `capabilities` property
+ */
+export type TestrunnerCapabilities = RequestedStandaloneCapabilities[] | RequestedMultiremoteCapabilities | RequestedMultiremoteCapabilities[];
+/**
+ * The capabilities that will be resolved within a worker instance, e.g. either
+ * a single set of capabilities or a single multiremote instance
+ */
+export type ResolvedTestrunnerCapabilities = WebdriverIO.Capabilities | Record<string, WebdriverIO.Capabilities>;
+/**
+ * The `capabilities` property is a required property when using the `remote` method.
+ */
+export interface WithRequestedCapabilities {
+    /**
+     * Defines the capabilities you want to run in your WebDriver session. Check out the
+     * documentation on [Capabilities](https://webdriver.io/docs/capabilities) for more details.
+     *
+     * @example
+     * ```js
+     * // WebDriver session
+     * const browser = remote({
+     *   capabilities: {
+     *     browserName: 'chrome',
+     *     browserVersion: 86
+     *     platformName: 'Windows 10'
+     *   }
+     * })
+     *
+     * // multiremote session
+     * const browser = remote({
+     *   capabilities: {
+     *     browserA: {
+     *       browserName: 'chrome',
+     *       browserVersion: 86
+     *       platformName: 'Windows 10'
+     *     },
+     *     browserB: {
+     *       browserName: 'firefox',
+     *       browserVersion: 74
+     *       platformName: 'Mac OS X'
+     *     }
+     *   }
+     * })
+     * ```
+     */
+    capabilities: RequestedStandaloneCapabilities;
 }
-export type RemoteCapability = DesiredCapabilities | W3CCapabilities | MultiRemoteCapabilities;
 /**
- * @deprecated use `WebdriverIO.Capabilities` instead
+ * The `capabilities` property is a required property when defining a testrunner configuration.
  */
-export interface DesiredCapabilities extends WebdriverIO.Capabilities, SauceLabsCapabilities, SauceLabsVisualCapabilities, TestingbotCapabilities, SeleniumRCCapabilities, GeckodriverCapabilities, IECapabilities, AppiumAndroidCapabilities, AppiumCapabilities, VendorExtensions, GridCapabilities, ChromeCapabilities, BrowserStackCapabilities, AppiumXCUITestCapabilities, LambdaTestCapabilities {
-    cssSelectorsEnabled?: boolean;
-    handlesAlerts?: boolean;
-    version?: string;
-    platform?: string;
-    public?: any;
-    loggingPrefs?: {
-        browser?: LoggingPreferences;
-        driver?: LoggingPreferences;
-        server?: LoggingPreferences;
-        client?: LoggingPreferences;
-    };
-    javascriptEnabled?: boolean;
-    databaseEnabled?: boolean;
-    locationContextEnabled?: boolean;
-    applicationCacheEnabled?: boolean;
-    browserConnectionEnabled?: boolean;
-    webStorageEnabled?: boolean;
-    acceptSslCerts?: boolean;
-    rotatable?: boolean;
-    nativeEvents?: boolean;
-    unexpectedAlertBehaviour?: string;
-    elementScrollBehavior?: number;
-    'webdriver.remote.sessionid'?: string;
-    'webdriver.remote.quietExceptions'?: boolean;
-    'selenium.server.url'?: string;
-    specs?: string[];
-    exclude?: string[];
-    excludeDriverLogs?: string[];
+export interface WithRequestedTestrunnerCapabilities {
+    /**
+     * Defines a set of capabilities you want to run in your WebDriver session. Check out the
+     * documentation on [Capabilities](https://webdriver.io/docs/capabilities) for more details.
+     *
+     * @example
+     * ```js
+     * // wdio.conf.js
+     * export const config = {
+     *   // define parallel running capabilities
+     *   capabilities: [{
+     *     browserName: 'safari',
+     *     platformName: 'MacOS 10.13',
+     *     ...
+     *   }, {
+     *     browserName: 'microsoftedge',
+     *     platformName: 'Windows 10',
+     *     ...
+     *   }, {
+     *     // using alwaysMatch and firstMatch
+     *   alwaysMatch: {
+     *     browserName: 'chrome',
+     *     browserVersion: 86
+     *      // ...
+     *   },
+     *   firstMatch: [{
+     *     browserName: 'chrome',
+     *      // ...
+     *   }]
+     * }
+     * ```
+     */
+    capabilities: RequestedStandaloneCapabilities[];
 }
-export interface VendorExtensions extends EdgeCapabilities, AppiumCapabilities, WebdriverIOCapabilities, WebdriverIO.WDIOVSCodeServiceOptions {
+/**
+ * The `capabilities` property is a required property when using the `remote` method to initiate a multiremote session.
+ */
+export interface WithRequestedMultiremoteCapabilities {
+    /**
+     * Defines the capabilities for each Multiremote client. Check out the
+     * documentation on [Capabilities](https://webdriver.io/docs/capabilities) for more details.
+     *
+     * @example
+     * ```
+     * // wdio.conf.js
+     * export const config = {
+     *   // multiremote example
+     *   capabilities: {
+     *     browserA: {
+     *       browserName: 'chrome',
+     *       browserVersion: 86
+     *       platformName: 'Windows 10'
+     *     },
+     *     browserB: {
+     *       browserName: 'firefox',
+     *       browserVersion: 74
+     *       platformName: 'Mac OS X'
+     *     }
+     *   }
+     * })
+     * ```
+     * // or with parallel multiremote sessions
+     * ```
+     * // wdio.conf.js
+     * export const config = {
+     *   capabilities: [{
+     *     browserA: {
+     *       port: 4444,
+     *       capabilities: {
+     *         browserName: 'chrome',
+     *         browserVersion: 86
+     *         platformName: 'Windows 10'
+     *       }
+     *     },
+     *     browserB: {
+     *       port: 4444,
+     *       capabilities: {
+     *         browserName: 'firefox',
+     *         browserVersion: 74
+     *         platformName: 'Mac OS X'
+     *       }
+     *     }
+     *   }, {
+     *     browserA: {
+     *       port: 4444,
+     *       capabilities: {
+     *         browserName: 'chrome',
+     *         browserVersion: 86
+     *         platformName: 'Windows 10'
+     *       }
+     *     },
+     *     browserB: {
+     *       port: 4444,
+     *       capabilities: {
+     *         browserName: 'firefox',
+     *         browserVersion: 74
+     *         platformName: 'Mac OS X'
+     *       }
+     *     }
+     *   }]
+     * })
+     * ```
+     */
+    capabilities: RequestedMultiremoteCapabilities | RequestedMultiremoteCapabilities[];
+}
+export interface VendorExtensions extends EdgeCapabilities, AppiumCapabilities, WebdriverIOCapabilities, WebdriverIO.WDIOVSCodeServiceOptions, AppiumXCUITestCapabilities, AppiumAndroidCapabilities {
     'selenoid:options'?: SelenoidOptions;
     'moon:options'?: MoonOptions;
     'tb:options'?: TestingbotCapabilities;
@@ -143,7 +276,6 @@ export interface VendorExtensions extends EdgeCapabilities, AppiumCapabilities,
     'goog:chromeOptions'?: ChromeOptions;
     'moz:firefoxOptions'?: FirefoxOptions;
     'moz:debuggerAddress'?: string | number;
-    firefox_profile?: string;
     'ms:edgeOptions'?: MicrosoftEdgeOptions;
     'ms:edgeChromium'?: MicrosoftEdgeOptions;
     'ms:experimental-webdriver'?: boolean;
@@ -155,10 +287,6 @@ export interface VendorExtensions extends EdgeCapabilities, AppiumCapabilities,
      * Selenium 4.0 Specific
      */
     'se:cdp'?: string;
-    /**
-     * @deprecated
-     */
-    testobject_api_key?: string;
 }
 export interface WebdriverIOCapabilities {
     /**
@@ -173,33 +301,22 @@ export interface WebdriverIOCapabilities {
     * Maximum number of total parallel running workers (per capability)
     */
     'wdio:maxInstances'?: number;
-    /**
-     * Maximum number of total parallel running workers (per capability)
-     * @deprecated please use `wdio:maxInstances` instead
-     */
-    maxInstances?: number;
     /**
     * Define specs for test execution. You can either specify a glob
     * pattern to match multiple files at once or wrap a glob or set of
     * paths into an array to run them within a single worker process.
     */
     'wdio:specs'?: string[];
-    /**
-     * Define specs for test execution. You can either specify a glob
-     * pattern to match multiple files at once or wrap a glob or set of
-     * paths into an array to run them within a single worker process.
-     * @deprecated please use `wdio:specs` instead
-     */
-    specs?: string[];
     /**
      * Exclude specs from test execution.
      */
     'wdio:exclude'?: string[];
     /**
-     * Exclude specs from test execution.
-     * @deprecated please use `wdio:exclude` instead
+     * If flag is set to `true` WebdriverIO will not automatically opt-in
+     * to the WebDriver BiDi protocol. This is useful if you want to use
+     * the WebDriver protocol only.
      */
-    exclude?: string[];
+    'wdio:enforceWebDriverClassic'?: boolean;
 }
 export interface ChromeOptions {
     /**
@@ -312,16 +429,6 @@ export type FirefoxLogLevels = 'trace' | 'debug' | 'config' | 'info' | 'warn' |
 export interface FirefoxLogObject {
     level: FirefoxLogLevels;
 }
-export interface GeckodriverCapabilities {
-    'firefox_binary'?: string;
-    firefoxProfileTemplate?: string;
-    captureNetworkTraffic?: boolean;
-    addCustomRequestHeaders?: boolean;
-    trustAllSSLCertificates?: boolean;
-    changeMaxConnections?: boolean;
-    profile?: string;
-    pageLoadingStrategy?: string;
-}
 export interface FirefoxOptions {
     debuggerAddress?: string;
     binary?: string;
@@ -362,20 +469,11 @@ export interface MoonOptions extends SelenoidOptions {
     };
     logLevel?: string;
 }
-export interface GridCapabilities {
-    seleniumProtocol?: string;
-    maxInstances?: number;
-    environment?: string;
-}
 export interface EdgeCapabilities {
     'ms:inPrivate'?: boolean;
     'ms:extensionPaths'?: string[];
     'ms:startPage'?: string;
 }
-export interface ChromeCapabilities {
-    chromeOptions?: ChromeOptions;
-    mobileEmulationEnabled?: boolean;
-}
 /**
  * Appium General W3C Capabilities
  *
@@ -438,6 +536,7 @@ export interface AppiumCapabilities {
     'appium:newCommandTimeout'?: number;
     'appium:language'?: string;
     'appium:locale'?: string;
+    'appium:animationCoolOffTimeout'?: number;
     /**
      * iOS Unique Device Identifier
      */
@@ -715,324 +814,503 @@ export interface AppiumXCUIProcessArguments {
 export interface AppiumXCUICommandTimeouts {
     [key: string]: any;
 }
-export interface IECapabilities {
-    'ie.forceCreateProcessApi'?: boolean;
-    'ie.browserCommandLineSwitches'?: string;
-    'ie.usePerProcessProxy'?: boolean;
-    'ie.ensureCleanSession'?: boolean;
-    'ie.setProxyByServer'?: boolean;
-    'ie.fileUploadDialogTimeout'?: number;
-    'ie.edgechromium'?: boolean;
-    'ie.edgepath'?: string;
-    ignoreProtectedModeSettings?: boolean;
-    ignoreZoomSetting?: boolean;
-    initialBrowserUrl?: string;
-    enablePersistentHover?: boolean;
-    enableElementCacheCleanup?: boolean;
-    requireWindowFocus?: boolean;
-    browserAttachTimeout?: number;
-    logFile?: string;
-    logLevel?: string;
-    host?: string;
-    extractPath?: string;
-    silent?: string;
-    killProcessesByName?: boolean;
-}
 /**
  * see also https://docs.saucelabs.com/dev/test-configuration-options
  */
 export interface SauceLabsCapabilities {
     /**
-     * Used to record test names for jobs and make it easier to find individual tests.
+     * Desktop Browser Capabilities: Sauce-Specific – Optional
+     * see https://docs.saucelabs.com/dev/test-configuration-options/#desktop-browser-capabilities-sauce-specific--optional
      */
-    name?: string;
     /**
-     * Used to associate jobs with a build number or app version, which is then displayed
-     * on both the Dashboard and Archives view
+     * Allows you to specify the ChromeDriver version you want to use for your tests.
+     * The default version of ChromeDriver when no value is specified depends on the version of Chrome used.
+     * As of Chrome 73, the major version of the driver and the browser must match.
      *
-     * @example `build-1234`
+     * Desktop Virtual Devices only.
+     *
+     * For a list of ChromeDriver versions, see chromedriver versions list.
+     * @see https://docs.saucelabs.com/dev/test-configuration-options/#chromedriverversion
+     * @see https://chromedriver.storage.googleapis.com/index.html
      */
-    build?: string | number;
+    chromedriverVersion?: string;
     /**
-     * User-defined tags for grouping and filtering jobs in the Dashboard and Archives view.
-     * @example
-     * ```
-     * ["tag1", "tag2", "tag3"]
-     * ```
+     * Specifies the Microsoft Edge driver version you want to use for your tests.
+     *
+     * Desktop Virtual Devices only.
+     *
+     * For a list of edgedriver versions, see the Microsoft Edge Driver website.
+     * @see https://docs.saucelabs.com/dev/test-configuration-options/#edgedriverversion
+     * @see https://developer.microsoft.com/en-us/microsoft-edge/tools/webdriver/
      */
-    tags?: string[];
+    edgedriverVersion?: string;
     /**
-     * User-defined custom data that will accept any valid JSON object, limited to 64KB in size.
-     * @example
-     * ```
-     * {
-     *   "release": "1.0",
-     *   "commit": "0k392a9dkjr",
-     *   "staging": true,
-     *   "execution_number": 5,
-     *   "server": "test.customer.com"
-     * }
-     * ```
+     * Specifies the Firefox GeckoDriver version.
+     * The default geckodriver version varies based on the version of Firefox specified.
+     *
+     * Desktop Virtual Devices only.
+     *
+     * For a list of geckodriver versions and the Firefox versions they support, see geckodriver Supported Platforms.
+     * @see https://docs.saucelabs.com/dev/test-configuration-options/#geckodriverversion
+     * @see https://firefox-source-docs.mozilla.org/testing/geckodriver/Support.html
      */
-    'custom-data'?: any;
+    geckodriverVersion?: string;
     /**
-     * If you are using Sauce Connect Proxy to to test an application that is behind a firewall
-     * or on your local machine, you must provide the identifier of the Sauce Connect tunnel to
-     * use. Check out [Basic Sauce Connect Proxy Setup](https://wiki.saucelabs.com/display/DOCS/Basic+Sauce+Connect+Proxy+Setup) for more information.
+     * Specifies the Internet Explorer Driver version. If no version is specified, it defaults to 2.53.1.
+     *
+     * Desktop Virtual Devices only.
+     *
+     * For a list of IE Driver versions, see Internet Explorer Driver Server CHANGELOG.
+     * @see https://docs.saucelabs.com/dev/test-configuration-options/#iedriverversion
+     * @see https://raw.githubusercontent.com/SeleniumHQ/selenium/trunk/cpp/iedriverserver/CHANGELOG
      */
-    tunnelIdentifier?: string;
+    iedriverVersion?: string;
     /**
-     * This desired capability will let the test job use any shared tunnels available from the
-     * specified parent account. i.e. any account that is upstream in the hierarchy. __If using a
-     * shared tunnel, you must specify both tunnelIdentifier and parentTunnel__. Check out the
-     * topic Using [Sauce Connect Tunnel Identifiers](https://wiki.saucelabs.com/display/DOCS/Using+Sauce+Connect+Tunnel+Identifiers) for more information.
+     * Specifies the Selenium version you want to use for your test.
+     * Sauce Labs will default to different versions, depending on the age of the browser and platform,
+     * and whether or not you're initializing a session with valid W3C syntax.
+     *
+     * Desktop Virtual Devices only.
+     * @see https://docs.saucelabs.com/dev/test-configuration-options/#seleniumversion
      */
-    parentTunnel?: string;
+    seleniumVersion?: string;
     /**
-     * This setting specifies which screen resolution should be used during the test session.
+     * Allows the browser to communicate directly with servers without going through a proxy.
+     * By default, Sauce routes traffic from Internet Explorer and Safari through an HTTP proxy server
+     * so that HTTPS connections with self-signed certificates will work.
      *
-     * @example `1280x1024`
+     * The proxy server can cause problems for some users, and this setting allows you to avoid it.
+     *
+     * Any test run with a Sauce Connect tunnel has to use the proxy and this flag will be ignored.
+     *
+     * Desktop Virtual Devices only.
+     * @see https://docs.saucelabs.com/dev/test-configuration-options/#avoidproxy
      */
-    screenResolution?: string;
+    avoidProxy?: boolean;
     /**
-     * Desktop Test VMs can be configured with custom time zones. This feature should work on all operating
-     * systems, however time zones on Windows VMs are approximate. The time zone will usually default to
-     * whatever local time zone is on your selected data center, but this cannot be guaranteed. You can
-     * find a complete list of timezones on Wikipedia. If the timeZone name has two or more or words
-     * (e.g., Los Angeles), you'll need to separate the words with either a space or an underscore. Sauce
-     * takes only location names (not their paths), as shown in the example below.
+     * Enables Extended Debugging features. This applies to Firefox and Chrome only.
+     * It records HAR files and console logs for both of these browsers.
+     * In Chrome, it also enables network interception, network and cpu throttling as well as access to network logs
+     * during the session. It is required to be true for capturePerformance. The default value is false.
      *
-     * @example Los_Angeles
-     * @example Honolulu
+     * Desktop Virtual Devices only.
+     * @see https://docs.saucelabs.com/dev/test-configuration-options/#extendeddebugging
+     * @see https://docs.saucelabs.com/insights/debug/
      */
-    timeZone?: string;
+    extendedDebugging?: boolean;
     /**
-     * By default, Sauce routes traffic from some WebDriver browsers (Edge, Internet Explorer and Safari)
-     * through the Selenium HTTP proxy server so that HTTPS connections with self-signed certificates
-     * work everywhere. The Selenium proxy server can cause problems for some users. If that's the case
-     * for you, you can configure Sauce to avoid using the proxy server and have browsers communicate
-     * directly with your servers.
+     * Enables Performance Capture feature.
+     * Sauce Performance Testing can be enabled by setting both extendedDebugging and capturePerformance to true.
+     * Default value is false.
      *
-     * __Don't Need the Selenium Proxy with Firefox or Google Chrome__
+     * Desktop Virtual Devices only.
+     * @see https://docs.saucelabs.com/dev/test-configuration-options/#captureperformance
+     * @see https://docs.saucelabs.com/performance/
+     */
+    capturePerformance?: boolean;
+    /**
+     * Specifies the screen resolution to be used during your test session.
+     * Default screen resolution for Sauce tests is 1024x768.
      *
-     * Firefox and Google Chrome under WebDriver aren't affected by this flag as they handle invalid
-     * certificates automatically and there isn't a need to proxy through Selenium.
+     * Desktop Virtual Devices only.
+     * @see https://docs.saucelabs.com/dev/test-configuration-options/#screenresolution
+     */
+    screenResolution?: string;
+    /**
+     * Sets command timeout in seconds.
+     * As a safety measure to prevent Selenium crashes from making your tests run indefinitely,
+     * we limit how long Selenium can take to run a command in our browsers.
+     * This is set to 300 seconds by default. The maximum command timeout value allowed is 600 seconds.
      *
-     * __Incompatible with Sauce Connect Proxy__
+     * Desktop Virtual Devices only.
+     * @see https://docs.saucelabs.com/dev/test-configuration-options/#commandtimeout
+     */
+    commandTimeout?: number;
+    /**
+     * Sets idle test timeout in seconds.
+     * As a safety measure to prevent tests from running too long after something has gone wrong,
+     * we limit how long a browser can wait for a test to send a new command.
+     * This is set to 90 seconds by default and limited to a maximum value of 1000 seconds.
      *
-     * This flag is incompatible with Sauce Connect Proxy.
+     * Desktop Virtual Devices only.
+     * @see https://docs.saucelabs.com/dev/test-configuration-options/#idletimeout
      */
-    avoidProxy?: boolean;
+    idleTimeout?: number;
     /**
-     * Sauce Labs supports several test result visibility levels, which control who can view the test
-     * details. The visibility level for a test can be set manually from the test results page, but
-     * also programmatically when starting a test or with our REST API. For more information about
-     * sharing test result, see the topics under Sharing the Results of Sauce Labs Tests.
-     *
-     * Available visibility levels are:
-     *
-     * - __public__: Making your test public means that it is accessible to everyone, and may be
-     *   listed on public web pages and indexed by search engines.
-     * - __public restricted__: If you want to share your job's result page and video, but keep
-     *   the logs only for you, you can certainly do so with public restricted visibility mode. This
-     *   visibility mode will hide the fancy job log as well as prohibit access to the raw Selenium log,
-     *   so that anonymous users with the link will be able to watch the video and screen shots but
-     *   won't be able to see what's being typed and done to get there.
-     * - __share__: You can also decide to make your test sharable. Making your test sharable means
-     *   that it is only accessible to people having valid link and it is not listed on publicly available
-     *   pages on saucelabs.com or indexed by search engines.
-     * - __team__: If you want to share your jobs with other team members (that were created as a sub-accounts
-     *   of one parent account), you can use team visibility mode. Making your test accessible by team means
-     *   that it is only accessible to people under the same root account as you.
-     * - __private__: If you don't want to share your test's result page and video with anyone, you should
-     *   use private job visibility mode. This way, only you (the owner) will be able to view assets and test
-     *   result page.
-     *
-     * @default private
+     * Mobile App Appium Capabilities: Sauce-Specific – Optional
+     * see https://docs.saucelabs.com/dev/test-configuration-options/#mobile-app-appium-capabilities-sauce-specific--optional
      */
-    public?: 'public' | 'public restricted' | 'share' | 'team' | 'private';
     /**
-     * You can provide a URL to an executable file, which will be downloaded and executed to configure the
-     * VM before the test starts. For faster performance, you may want to upload the executable to [Sauce Storage](https://wiki.saucelabs.com/display/DOCS/Uploading+your+Application+to+Emulators+and+Simulators),
-     * a private temporary storage space. This capability takes a JSON object with four main keys.
-     * Check out the topics under [Using Pre-Run Executables to Configure Browsers and Virtual Machines](https://wiki.saucelabs.com/display/DOCS/Using+Pre-Run+Executables+to+Configure+Browsers+and+Virtual+Machines) for
-     * more information.
+     * Specifies the Appium driver version you want to use.
+     * For most use cases, setting the appiumVersion is unnecessary because Sauce Labs defaults to the version that supports the broadest number of device combinations.
+     * Sauce Labs advises against setting this property unless you need to test a particular Appium feature or patch.
      *
-     * __Running AutoIt Scripts__
+     * Virtual and Real Devices only.
+     * @see https://docs.saucelabs.com/dev/test-configuration-options/#appiumversion
+     */
+    appiumVersion?: string;
+    /**
+     * Specifies the orientation of the virtual skin and screen during the test.
      *
-     * If you want to run an AutoIt script during your test, compile it as an .exe, send it using this
-     * capability, and set background to true to allow AutoIt to continue running throughout the full
-     * duration of your test.
+     * Virtual Devices only.
+     * @see https://docs.saucelabs.com/dev/test-configuration-options/#deviceorientation
+     */
+    deviceOrientation?: 'portrait' | 'landscape';
+    /**
+     * If your app creates an extra log then you can use the customLogFiles to store those additional logs in the "Logs" tab of the executed automated session.
+     * It is created in the form of a list of search filters that enumerate after an app test to locate text files to upload as logs.
+     * Files are uploaded with the .log extension appended. The search paths are rooted at the application under test.
      *
-     * __Using Multiple Pre-Run Executables__
+     * Virtual Devices only.
+     * @see https://docs.saucelabs.com/dev/test-configuration-options/#customlogfiles
+     */
+    customLogFiles?: string[];
+    /**
+     * By default, our emulator uses software rendering to handle graphics for maximum compatibility.
+     * This involves the CPU calculating how everything looks on your app's screen.
+     * However, this could lead to an emulator crash when testing apps with intricate or heavy graphical elements.
+     * To mitigate this, use the hardware rendering option by specifying "android.gpu.mode"="hardware" in your test capabilities.
      *
-     * If you need to send multiple pre-run executables, the best way is to bundle them into a single
-     * executable file, such as a self-extracting zip file.
+     * Android Virtual Devices only.
+     * @see https://docs.saucelabs.com/dev/test-configuration-options/#androidgpumode
      */
-    prerun?: {
-        executable: string;
-        args: string[];
-        background: boolean;
-        timeout: number;
-    };
+    'android.gpu.mode'?: 'software' | 'hardware';
     /**
-     * By default, Sauce Labs records a video of every test you run. This is generally handy for debugging
-     * failing tests, as well as having a visual confirmation that certain feature works (or still works!)
-     * However, there is an added wait time for screen recording during a test run.
+     * Android allows apps to use the full screen, hiding the status bar and navigation bar.
+     * This is called "immersive mode". When you run an Android test, the device will show a popup asking if you want to allow the app to use immersive mode.
+     * This popup can interfere with your test, and by default we disable it.
+     * If you want to enable it, set disableImmersiveModePopUp to false.
+     *
+     * Android Virtual Devices only.
+     * @see https://docs.saucelabs.com/dev/test-configuration-options/#disableimmersivemodepopup
      */
-    recordVideo?: boolean;
+    disableImmersiveModePopUp?: boolean;
     /**
-     * As an alternative to disabling video recording, the  videoUploadOnPass  setting will let you
-     * discard videos for passing tests identified using the passed setting. This disables video
-     * post-processing and uploading that may otherwise consume some extra time after your test is complete.
+     * Sets up the device pin code for the automated test session.
+     * This capability sets your device in the state required for your application to launch successfully.
+     *
+     * Real Devices only.
+     * @see https://docs.saucelabs.com/dev/test-configuration-options/#disableimmersivemodepopup
      */
-    videoUploadOnPass?: boolean;
+    setupDeviceLock?: boolean;
     /**
-     * Sauce Labs captures step-by-step screenshots of every test you run. Most users find it very
-     * useful to get a quick overview of what happened without having to watch the complete video.
-     * However, this feature may add some extra time to your tests. You can avoid this by optionally
-     * turning off this feature.
+     * Use this capability to select only tablet devices for testing.
+     *
+     * Real Devices only.
+     * @see https://docs.saucelabs.com/dev/test-configuration-options/#tabletonly
      */
-    recordScreenshots?: boolean;
+    tabletOnly?: boolean;
     /**
-     * By default, Sauce creates a log of all the actions that you execute to create a report for the
-     * test run that lets you troubleshoot test failures more easily.
+     * Use this capability to select only phone devices for testing.
      *
-     * __Note:__ Selenium Logs Are Still Recorded
+     * Real Devices only.
+     * @see https://docs.saucelabs.com/dev/test-configuration-options/#phoneonly
+     */
+    phoneOnly?: boolean;
+    /**
+     * Use this capability to select only private devices for testing.
      *
-     * This option only disables recording of the log.json file. The selenium-server.log will still be
-     * recorded even if you choose to disable recording of the log.json.
+     * Private Real Devices only.
+     * @see https://docs.saucelabs.com/dev/test-configuration-options/#privatedevicesonly
      */
-    recordLogs?: boolean;
+    privateDevicesOnly?: boolean;
     /**
-     * If you have multiple new jobs waiting to start (i.e., across a collection of sub-accounts), jobs
-     * with a lower priority number take precedence over jobs with a higher number. So, for example, if
-     * you have multiple jobs simultaneously waiting to start, we'll first attempt to find resources to
-     * start all the jobs with priority 0, then all the jobs with priority 1, etc. When we run out of
-     * available virtual machines, or when you hit your concurrency limit, any jobs not yet started will
-     * wait. Within each priority level, jobs that have been waiting the longest take precedence.
+     * Use this capability to select only public devices for testing.
      *
-     * @default 0
+     * Real Devices only.
+     * @see https://docs.saucelabs.com/dev/test-configuration-options/#publicdevicesonly
      */
-    priority?: number;
+    publicDevicesOnly?: boolean;
     /**
-     * Enable [Extended Debugging Capabilities](https://wiki.saucelabs.com/pages/viewpage.action?pageId=70072943).
+     * Use this capability to allocate only devices connected to a carrier network.
      *
-     * @default false
+     * Private Real Devices only.
+     * @see https://docs.saucelabs.com/dev/test-configuration-options/#carrierconnectivityonly
      */
-    extendedDebugging?: boolean;
+    carrierConnectivityOnly?: boolean;
     /**
-     * Enable [Frontend Performance](https://wiki.saucelabs.com/display/DOCS/Measure+Page+Load+Performance+Using+Test+Automation) capturing capabilities.
+     * Keeps the device allocated to you between test sessions and bypasses the device cleaning process and session exit that occurs by default after each test completes.
+     * Normally, you'd need to start over and reopen another device.
+     * You'll need to launch your next test within 10 seconds of your previous test ending
+     * to ensure that the same device will be allocated for the test (not cleaned or reset).
+     *
+     * Real Devices only.
+     * @see https://docs.saucelabs.com/dev/test-configuration-options/#cacheid
      */
-    capturePerformance?: boolean;
+    cacheId?: string;
     /**
-     * We do not recommend to use this option.
-     * @deprecated
+     * Controls Sauce Labs default resigning (iOS) or instrumentation (Android) of mobile apps installed on our devices.
+     *
+     * Real Devices only.
+     * @see https://docs.saucelabs.com/dev/test-configuration-options/#resigningenabled
      */
-    seleniumVersion?: string;
+    resigningEnabled?: boolean;
     /**
-     * Chromedriver versions are pinned to the Chrome version you have defined in your capabilities.
-     * Only define a custom `chromedriverVersion` if you know what you do.
+     * Enables the camera image injection feature. resigningEnabled needs to be enabled if this is set to true.
      *
-     * @deprecated
+     * Real Devices only.
+     * @see https://docs.saucelabs.com/mobile-apps/features/camera-image-injection/
+     * @see https://docs.saucelabs.com/dev/test-configuration-options/#saucelabsimageinjectionenabled
      */
-    chromedriverVersion?: string;
+    sauceLabsImageInjectionEnabled?: boolean;
     /**
-     * The Internet Explorer Driver defaults to version 2.53.1 when no version is specified.
+     * Bypasses the restriction on taking screenshots for secure screens (i.e., secure text entry). resigningEnabled needs to be enabled if this is set to true.
      *
-     * Note that the versions of Internet Explorer Driver we have available correspond to major Selenium
-     * releases - we do not have all the minor point releases (e.g. 3.12.0.4) available.
+     * Android Real Devices only.
+     * @see https://docs.saucelabs.com/dev/test-configuration-options/#saucelabsbypassscreenshotrestriction
+     */
+    sauceLabsBypassScreenshotRestriction?: boolean;
+    /**
+     * Enables the interception of biometric input, allowing the test to simulate Touch ID interactions (not a Sauce Labs-specific capability).
+     * resigningEnabled needs to be enabled if this is set to true.
      *
-     * We recommend setting the Selenium Version (see above) to correspond with the Internet Explorer Driver
-     * version you select.
+     * Real Devices only.
+     * @see https://docs.saucelabs.com/dev/test-configuration-options/#allowtouchidenroll
+     */
+    allowTouchIdEnroll?: boolean;
+    /**
+     * Enables audio recording in your iOS and Android native mobile app tests.
+     * The audio will be part of the Test Results page video file, which you can play back and download in our built-in media player.
+     * The default value is false.
      *
-     * Sauce Labs supports launching 64-bit IE on our 64-bit VMs: Windows 7, Windows 8, and Windows 8.1.
-     * This provides a workaround for two known Selenium issues:
-     * - Using a 32 bit driver on a 64 bit operating system causes Selenium's screenshot feature to only
-     *   capture the part of the page currently visible in the browser viewport Selenium Issue 5876.
-     * - Using a 64 bit driver on a 64 bit operating system causes text entry to be extremely slow
-     *   Selenium Issue 5516.
+     * Real Devices only.
+     * @see https://docs.saucelabs.com/dev/test-configuration-options/#audiocapture
+     */
+    audioCapture?: boolean;
+    /**
+     * Enables mobile app instrumentation (Android or iOS) and recording of HTTP/HTTPS network traffic for debugging purposes.
+     * API calls are collected into a HAR file, which you can view and download from your Test Results > Network tab console.
+     * The default value is false.
      *
-     * @deprecated
+     * Real Devices only.
+     * @see https://docs.saucelabs.com/dev/test-configuration-options/#networkcapture
      */
-    iedriverVersion?: string;
+    networkCapture?: boolean;
     /**
-     * For Firefox version 80 and above, geckodriver defaults to latest driver version 0.27.0 when no
-     * version is specified.
+     * Enables the use of the app's private app container directory instead of the shared app group container directory.
+     * For testing on the Real Device Cloud, the app gets resigned, which is why the shared directory is not accessible.
      *
-     * @deprecated
+     * iOS Real Devices only.
+     * @see https://docs.saucelabs.com/dev/test-configuration-options/#groupfolderredirectenabled
      */
-    geckodriverVersion?: string;
+    groupFolderRedirectEnabled?: boolean;
     /**
-     * As a safety measure to prevent tests from running indefinitely, Sauce limits the duration of
-     * tests to 30 minutes by default. You can adjust this limit on per-job basis and the maximum
-     * value is 10800 seconds.
+     * Use this capability to enable animations for Android real devices by setting it to true. By default, animations are disabled.
      *
-     * __Don't Exceed 30 Minutes__
+     * Android Real Devices only.
+     * @see https://docs.saucelabs.com/dev/test-configuration-options/#enableanimations
+     */
+    enableAnimations?: boolean;
+    /**
+     * Delays system alerts, such as alerts asking for permission to access the camera, to prevent app crashes at startup.
+     * resigningEnabled needs to be enabled if this is set to true.
      *
-     * A test should never last more than 30 minutes and ideally should take less than five minutes.
-     * The 3 hour maximum exists mainly to ease the transition of new users migrating long running
-     * tests to Sauce Labs.
+     * iOS Real Devices only.
+     * @see https://docs.saucelabs.com/dev/test-configuration-options/#systemalertsdelayenabled
+     */
+    systemAlertsDelayEnabled?: boolean;
+    /**
+     * Specify the amount of time (in milliseconds) that the test should be allowed to find and assign an available device before the test will fail.
+     * The default value is 900000 milliseconds (15 minutes) and the max is 1800000 milliseconds (30 minutes).
      *
-     * While our test VMs respect the maxDuration desired capability when it's set in tests, it may
-     * not always be precise. Tests will never be timed out before their maxDuration has elapsed and
-     * in most cases, they will be timed out very shortly after their maxDuration has elapsed (usually
-     * less than 1 second). But, in some rare cases, such as when the test VM is suffering performance
-     * problems, they can be allowed to run longer (30 seconds or more).
+     * Real Devices only.
+     * @see https://docs.saucelabs.com/dev/test-configuration-options/#sessioncreationtimeout
+     */
+    sessionCreationTimeout?: boolean;
+    /**
+     * Specify the amount of automatic retries that Sauce Labs will execute to find and assign an available device before the test will fail.
+     * The default value is 1 and the max is 3.
      *
-     * @default 1800
+     * Real Devices only.
+     * @see https://docs.saucelabs.com/dev/test-configuration-options/#sessioncreationretry
+     */
+    sessionCreationRetry?: number;
+    /**
+     * Desktop and Mobile Capabilities: Sauce-Specific – Optional
+     * see https://docs.saucelabs.com/dev/test-configuration-options/#desktop-and-mobile-capabilities-sauce-specific--optional
      */
-    maxDuration?: number;
     /**
-     * As a safety measure to prevent Selenium crashes from making your tests run indefinitely, Sauce
-     * limits how long Selenium can take to run a command in our browsers. This is set to 300 seconds
-     * by default. The value of this setting is given in seconds. The maximum command timeout value
-     * allowed is 600 seconds.
+     * Used to record test names for jobs and make it easier to find individual tests.
+     * @see https://docs.saucelabs.com/dev/test-configuration-options/#name
+     */
+    name?: string;
+    /**
+     * Used to associate jobs with a build number or app version, which is then displayed
+     * on both the Dashboard and Archives view
      *
-     * @default 300
+     * @see https://docs.saucelabs.com/dev/test-configuration-options/#build
+     * @example `build-1234`
      */
-    commandTimeout?: number;
+    build?: string | number;
     /**
-     * As a safety measure to prevent tests from running too long after something has gone wrong, Sauce
-     * limits how long a browser can wait for a test to send a new command. This is set to 90 seconds
-     * by default and limited to a maximum value of 1000 seconds. You can adjust this limit on a per-job
-     * basis. The value of this setting is given in seconds.
+     * User-defined tags for grouping and filtering jobs in the Dashboard and Archives view.
+     * @see https://docs.saucelabs.com/dev/test-configuration-options/#tags
+     * @example
+     * ```
+     * ["tag1", "tag2", "tag3"]
+     * ```
+     */
+    tags?: string[];
+    /**
+     * Sets your Sauce Labs username for a test.
      *
-     * @default 90
+     * You can either set "username" in capabilities or specify it in the Sauce URL as Basic Authentication. For Visual Tests), this must be set in capabilities.
+     * @see https://docs.saucelabs.com/dev/test-configuration-options/#username
      */
-    idleTimeout?: number;
+    username?: string;
     /**
-     * Enables the interception of biometric input, allowing the test to
-     * simulate Touch ID interactions (not a Sauce Labs-specific capability).
+     * Sets your Sauce Labs access key for the test.
      *
-     * @default false
+     * You can either set "accessKey" in capabilities or specify it in the Sauce URL as Basic Authentication. For Visual Tests, this must be set in capabilities.
+     * @see https://docs.saucelabs.com/dev/test-configuration-options/#accesskey
      */
-    allowTouchIdEnroll?: boolean;
+    accessKey?: string;
     /**
-     * Keeps a device allocated to you between test sessions, bypassing the
-     * device cleaning process and session exit that occurs by default after
-     * each test completes. Normally, you'd need to start over and reopen
-     * another device. You'll need to launch your next test within 10 seconds
-     * of your previous test ending to ensure that the same device will be
-     * allocated for the test (not cleaned or reset).
+     * User-defined custom data that will accept any valid JSON object, limited to 64KB in size.
+     * @see https://docs.saucelabs.com/dev/test-configuration-options/#custom-data
+     * @example
+     * ```
+     * {
+     *   "release": "1.0",
+     *   "commit": "0k392a9dkjr",
+     *   "staging": true,
+     *   "execution_number": 5,
+     *   "server": "test.customer.com"
+     * }
+     * ```
+     */
+    'custom-data'?: any;
+    /**
+     * We support several test/job result visibility levels, which control who can view the test details.
+     * The visibility level for a test can be set manually from the test results page, but also programmatically when starting a test or with our REST API.
+     * For more information about sharing test results, see the topics under Sharing the Results of Sauce Labs Tests.
      *
-     * @default *randomized string*
+     * Desktop and Virtual Devices only.
+     *
+     * @see https://docs.saucelabs.com/test-results/sharing-test-results/
      */
-    cacheId?: string;
+    public?: 'public' | 'public restricted' | 'share' | 'team' | 'private';
     /**
-     * Specifies the Appium driver version you want to use. For most use cases,
-     * setting the appiumVersion is unnecessary because Sauce Labs defaults to
-     * the version that supports the broadest number of device combinations.
-     * Sauce Labs advises against setting this property unless you need to test
-     * a particular Appium feature or patch.
+     * Specify a Sauce Connect tunnel to establish connectivity with Sauce Labs for your test.
+     * Tunnels allow you to test an app that is behind a firewall or on your local machine by providing a secure connection to the Sauce Labs platform.
+     * @see https://docs.saucelabs.com/secure-connections/sauce-connect/setup-configuration/basic-setup/
+     * @see https://docs.saucelabs.com/dev/test-configuration-options/#tunnelname
      */
-    appiumVersion?: string;
+    tunnelName?: string;
     /**
-     * Controls Sauce Labs default resigning (iOS) or instrumentation (Android)
-     * of mobile apps installed on our devices.
-     * @default true
+     * Specify a Sauce Connect tunnel name to establish connectivity with a Sauce Labs test platform. This is an alias for tunnelName.
+     * @see https://docs.saucelabs.com/dev/test-configuration-options/#tunnelidentifier
+     * @deprecated
      */
-    resigningEnabled?: boolean;
+    tunnelIdentifier?: string;
+    /**
+     * If the tunnelName you've specified to establish connectivity with a Sauce Labs test platform is a shared tunnel,
+     * and you are not the user who created the tunnel, you must identify the Sauce Labs user who did create the tunnel in order to use it for your test.
+     * @see https://docs.saucelabs.com/secure-connections/sauce-connect/setup-configuration/basic-setup/#using-tunnel-names
+     * @see https://docs.saucelabs.com/dev/test-configuration-options/#tunnelowner
+     */
+    tunnelOwner?: string;
+    /**
+     * If the tunnelName (or tunnelIdentifier) you've specified to establish connectivity with a Sauce Labs test platform is a shared tunnel,
+     * and you are not the user who created the tunnel, you must identify the Sauce Labs user who did create the tunnel in order to use it for your test.
+     * This is an alias for tunnelOwner.
+     * @see https://docs.saucelabs.com/dev/test-configuration-options/#parenttunnel
+     * @deprecated
+     */
+    parentTunnel?: string;
+    /**
+     * Use this to disable video recording. By default, Sauce Labs records a video of every test you run.
+     * Disabling video recording can be useful for debugging failing tests as well as having a visual confirmation that a certain feature works (or still works).
+     * However, there is an added wait time for screen recording during a test run.
+     * @see https://docs.saucelabs.com/dev/test-configuration-options/#recordvideo
+     */
+    recordVideo?: boolean;
+    /**
+     * Disables video upload for passing tests. videoUploadOnPass is an alternative to recordVideo; it lets you discard videos for tests you've marked as passing.
+     * It disables video post-processing and uploading that may otherwise consume some extra time after your test is complete.
+     * @see https://docs.saucelabs.com/dev/test-configuration-options/#videouploadonpass
+     */
+    videoUploadOnPass?: boolean;
+    /**
+     * Disables step-by-step screenshots. In addition to capturing video, Sauce Labs captures step-by-step screenshots of every test you run.
+     * Most users find it very useful to get a quick overview of what happened without having to watch the complete video.
+     * However, this feature may add some extra time to your tests.
+     * @see https://docs.saucelabs.com/dev/test-configuration-options/#recordscreenshots
+     */
+    recordScreenshots?: boolean;
+    /**
+     * In the same way Sauce Labs captures step-by-step screenshots, you can capture the HTML source at each step of a test.
+     * This feature is disabled by default, but when it is enabled you can view the HTML source captures on the Test Results page.
+     * @see https://docs.saucelabs.com/dev/test-configuration-options/#capturehtml
+     */
+    captureHtml?: boolean;
+    /**
+     * Disables log recording. By default, Sauce creates a log of all the actions that you execute to create a report for the test run
+     * that lets you troubleshoot test failures more easily.
+     * This option disables only the recording of the log.json file; the selenium-server.log will still be recorded.
+     * @see https://docs.saucelabs.com/dev/test-configuration-options/#recordlogs
+     */
+    recordLogs?: boolean;
+    /**
+     * Desktop and Virtual Device Capabilities: Sauce-Specific – Optional
+     * see https://docs.saucelabs.com/dev/test-configuration-options/#desktop-and-virtual-device-capabilities-sauce-specific--optional
+     */
+    /**
+     * Sets maximum test duration in seconds. As a safety measure to prevent tests from running indefinitely,
+     * the default is 1,800 seconds (30 minutes) and the maximum is 10,800 seconds (three hours).
+     *
+     * Desktop and Virtual Devices only.
+     * @see https://docs.saucelabs.com/dev/test-configuration-options/#maxduration
+     */
+    maxDuration?: number;
+    /**
+     * Setting to prioritize jobs. If you have multiple new jobs waiting to start (i.e., across a collection of sub-accounts),
+     * jobs with a lower priority number take precedence over jobs with a higher number.
+     *
+     * So, for example, if you have multiple jobs simultaneously waiting to start,
+     *  we'll first attempt to find resources to start all the jobs with priority 0,then all the jobs with priority 1, etc.
+     *
+     * When we run out of available virtual machines, or when you hit your concurrency limit, any jobs not yet started will wait.
+     * Within each priority level, jobs that have been waiting the longest take precedence.
+     *
+     * Desktop and Virtual Devices only.
+     * @see https://docs.saucelabs.com/dev/test-configuration-options/#priority
+     */
+    priority?: number;
+    /**
+     * Allows you to set a custom time zone for your test based on a city name. Most major cities are supported.
+     *
+     * Desktop and Virtual Devices only.
+     * @example Los_Angeles
+     * @example Honolulu
+     * @see https://docs.saucelabs.com/dev/test-configuration-options/#timezone
+     */
+    timeZone?: string;
+    /**
+     * You can provide a URL to an executable file, which will be downloaded and executed to configure the
+     * VM before the test starts. For faster performance, you may want to upload the executable to [Sauce Storage](https://wiki.saucelabs.com/display/DOCS/Uploading+your+Application+to+Emulators+and+Simulators),
+     * a private temporary storage space. This capability takes a JSON object with four main keys.
+     * Check out the topics under [Using Pre-Run Executables to Configure Browsers and Virtual Machines](https://wiki.saucelabs.com/display/DOCS/Using+Pre-Run+Executables+to+Configure+Browsers+and+Virtual+Machines) for
+     * more information.
+     *
+     * __Running AutoIt Scripts__
+     *
+     * If you want to run an AutoIt script during your test, compile it as an .exe, send it using this
+     * capability, and set background to true to allow AutoIt to continue running throughout the full
+     * duration of your test.
+     *
+     * __Using Multiple Pre-Run Executables__
+     *
+     * If you need to send multiple pre-run executables, the best way is to bundle them into a single
+     * executable file, such as a self-extracting zip file.
+     */
+    prerun?: {
+        executable: string;
+        args: string[];
+        background: boolean;
+        timeout: number;
+    };
+    recordDeviceVitals?: boolean;
 }
 export interface LambdaTestCapabilities {
     username?: string;
@@ -1112,7 +1390,7 @@ export interface BrowserStackCapabilities {
     os?: string;
     os_version?: string;
     osVersion?: string;
-    desired?: DesiredCapabilities;
+    desired?: unknown;
     device?: string;
     platformName?: string;
     /**
@@ -1321,6 +1599,16 @@ export interface BrowserStackCapabilities {
     uploadMedia?: Array<string>;
     enablePasscode?: boolean;
     deviceLogs?: boolean;
+    /**
+     * Disable re-signing of Enterprise signed app uploaded on BrowserStack
+     * @default true
+     */
+    resignApp?: boolean;
+    /**
+     * Hides data that you send to or retrieve from the remote browsers through the following commands:
+     * Example: 'setValues, getValues, setCookies, getCookies'
+     */
+    maskCommands?: string;
 }
 export interface SauceLabsVisualCapabilities {
     /**
@@ -1412,9 +1700,11 @@ export interface SauceLabsVisualCapabilities {
  * https://testingbot.com/support/other/test-options#platform
  */
 export interface TestingbotCapabilities {
+    appiumVersion?: string;
+    appiumPlugins?: string[];
     name?: string;
     tags?: string[];
-    build?: string | number | number;
+    build?: string | number;
     public?: boolean;
     'tunnel-identifier'?: string;
     realDevice?: boolean;
@@ -1424,26 +1714,19 @@ export interface TestingbotCapabilities {
     edgedriverVersion?: string;
     geckodriverVersion?: string;
     operaDriverVersion?: string;
+    'screen-resolution'?: string;
     timeZone?: string;
+    'throttle_network'?: any;
+    tabletOnly?: boolean;
+    phoneOnly?: boolean;
+    recordLogs?: boolean;
+    screenshot?: boolean;
+    screenrecorder?: boolean;
+    maxDuration?: number;
     upload?: string;
     'testingbot.geoCountryCode'?: string;
     idletimeout?: number;
     'load-extension'?: string;
 }
-export interface SeleniumRCCapabilities {
-    commandLineFlags?: string;
-    executablePath?: string;
-    timeoutInSeconds?: number;
-    onlyProxySeleniumTraffic?: boolean;
-    avoidProxy?: boolean;
-    proxyEverything?: boolean;
-    proxyRequired?: boolean;
-    browserSideLog?: boolean;
-    optionsSet?: boolean;
-    singleWindow?: boolean;
-    dontInjectRegex?: RegExp;
-    userJSInjection?: boolean;
-    userExtensions?: string;
-}
 export {};
 //# sourceMappingURL=Capabilities.d.ts.map