documentation: new capabilities management.

Author: lucashimpens

source/src/main/resources/documentation/D1/include/en/testmanagement_runtestcase_en.adoc

@@ -54,7 +54,70 @@ However, if the user changes this value, it will be overriden by his selection.
 
 'Save Robot Preferencies' button save these settings in the browser cache of the device.
 
-The selected robot can be edited using the left button. A new robot can be created using the right one. 
+The selected robot can be edited using the left button. A new robot can be created using the right one.
+
+=== Robot Capabilities
+
+When creating or updating a robot, you can specify capabilities in the 'Capabilities' tab of the robot modal window.
+Appium 2 and Selenium 4 use the W3C protocol to apply the capabilities to the robot. Therefore, it's essential to follow the correct syntax to ensure compliance with the W3C protocol.
+
+==== Basic WebDriver Capabilities
+
+The syntax remains mostly the same, with the exceptions of 'version' and 'platform', which have been replaced by 'browserVersion' and 'platformName' respectively.
+You can find the list of W3C WebDriver standard capabilities here:
+https://www.w3.org/TR/webdriver1/#capabilities.
+
+==== Appium Capabilities
+
+With Appium 2, each Appium capability name must be prefixed with the `appium` prefix.
+When defining Appium capabilities in the **Capabilities** tab, you must prefix the capability name like this: `<prefix>:<capability>`.
+
+For example:
+
+* `appium:app` (instead of just `app`)
+* `appium:appActivity` (instead of `appActivity`)
+* ...
+
+You can find the official documentation provided by Appium:
+
+* General capabilities: https://appium.io/docs/en/2.0/guides/caps/
+* UIAutomator2 driver capabilities: https://github.com/appium/appium-uiautomator2-driver
+* XCUITest driver capabilities: https://appium.github.io/appium-xcuitest-driver/latest/reference/capabilities/
+
+==== Cloud Provider Capabilities
+
+Cerberus supports the following 3 cloud testing providers:
+
+* BrowserStack
+* LambdaTest
+* Kobiton
+
+To define specific cloud capabilities, in addition to those generated by Cerberus when launching the test, you must prefix the capability name as follows: `<prefix>:<capability>`.
+
+Prefixes are specific to each testing cloud provider:
+
+* `bstack` for BrowserStack (e.g., `bstack:buildName`; `bstack:sessionName`; ...)
+* `lt` for LambdaTest (e.g., `lt:build`; `lt:name`; ...)
+* `kobiton` for Kobiton (e.g., `kobiton:sessionName`; `kobiton:sessionDescription`; ...)
+
+Each of these testing cloud providers provides documentation on capabilities:
+
+* BrowserStack:
+  - Web Automate capabilities: https://www.browserstack.com/docs/automate/capabilities
+  - App Automate capabilities: https://www.browserstack.com/docs/app-automate/capabilities
+* LambdaTest:
+  - Capabilities Generator: https://www.lambdatest.com/capabilities-generator/
+* Kobiton:
+  - Launching an Appium 2 session on Kobiton: https://docs.kobiton.com/automation-testing/basic-appium-server/launch-a-basic-appium-2-session
+  - Available Kobiton capabilities: https://docs.kobiton.com/automation-testing/capabilities/available-capabilities#_kobiton_capabilities
+
+==== Capabilities File
+
+You can view the capabilities used in your tests by navigating to the **Robot** tab in the **Execution Report**.
+Two files are available:
+
+* **Robot caps**: The list of capabilities provided by you and Cerberus to the robot.
+* **Robot server caps**: The capabilities generated by the server (Selenium or Appium). This file combines **Robot caps** and additional server-specific capabilities.
 
 === Execution settings