robotframework-plugins 2026.11.0__py3-none-any.whl

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (199) hide show
  1. robotframework_plugins/__init__.py +14 -0
  2. robotframework_plugins/_assets/catalog.json +143 -0
  3. robotframework_plugins/_assets/plugins/rf-agentskills/.claude-plugin/plugin.json +25 -0
  4. robotframework_plugins/_assets/plugins/rf-agentskills/CHANGELOG.md +198 -0
  5. robotframework_plugins/_assets/plugins/rf-agentskills/README.md +27 -0
  6. robotframework_plugins/_assets/plugins/rf-agentskills/catalog.yaml +25 -0
  7. robotframework_plugins/_assets/plugins/rf-api/.claude-plugin/plugin.json +25 -0
  8. robotframework_plugins/_assets/plugins/rf-api/CHANGELOG.md +9 -0
  9. robotframework_plugins/_assets/plugins/rf-api/README.md +27 -0
  10. robotframework_plugins/_assets/plugins/rf-api/catalog.yaml +27 -0
  11. robotframework_plugins/_assets/plugins/rf-api/skills/rf-requests/SKILL.md +113 -0
  12. robotframework_plugins/_assets/plugins/rf-api/skills/rf-requests/assets/examples/authentication-patterns.robot +39 -0
  13. robotframework_plugins/_assets/plugins/rf-api/skills/rf-requests/assets/examples/basic-crud.robot +46 -0
  14. robotframework_plugins/_assets/plugins/rf-api/skills/rf-requests/assets/examples/file-upload.robot +28 -0
  15. robotframework_plugins/_assets/plugins/rf-api/skills/rf-requests/assets/examples/session-handling.robot +48 -0
  16. robotframework_plugins/_assets/plugins/rf-api/skills/rf-requests/references/async-jobs.md +42 -0
  17. robotframework_plugins/_assets/plugins/rf-api/skills/rf-requests/references/authentication.md +58 -0
  18. robotframework_plugins/_assets/plugins/rf-api/skills/rf-requests/references/install.md +10 -0
  19. robotframework_plugins/_assets/plugins/rf-api/skills/rf-requests/references/loose-assertions.md +20 -0
  20. robotframework_plugins/_assets/plugins/rf-api/skills/rf-requests/references/request-options.md +90 -0
  21. robotframework_plugins/_assets/plugins/rf-api/skills/rf-requests/references/response-validation.md +64 -0
  22. robotframework_plugins/_assets/plugins/rf-api/skills/rf-requests/references/troubleshooting.md +64 -0
  23. robotframework_plugins/_assets/plugins/rf-api/skills/rf-restinstance/SKILL.md +120 -0
  24. robotframework_plugins/_assets/plugins/rf-api/skills/rf-restinstance/assets/examples/basic-rest.robot +51 -0
  25. robotframework_plugins/_assets/plugins/rf-api/skills/rf-restinstance/assets/examples/schema-validation.robot +38 -0
  26. robotframework_plugins/_assets/plugins/rf-api/skills/rf-restinstance/assets/examples/schemas/user.json +10 -0
  27. robotframework_plugins/_assets/plugins/rf-api/skills/rf-restinstance/references/authentication.md +61 -0
  28. robotframework_plugins/_assets/plugins/rf-api/skills/rf-restinstance/references/install.md +11 -0
  29. robotframework_plugins/_assets/plugins/rf-api/skills/rf-restinstance/references/json-handling.md +89 -0
  30. robotframework_plugins/_assets/plugins/rf-api/skills/rf-restinstance/references/loose-assertions.md +18 -0
  31. robotframework_plugins/_assets/plugins/rf-api/skills/rf-restinstance/references/migrate-from-requests.md +15 -0
  32. robotframework_plugins/_assets/plugins/rf-api/skills/rf-restinstance/references/schema-validation.md +85 -0
  33. robotframework_plugins/_assets/plugins/rf-api/skills/rf-restinstance/references/troubleshooting.md +68 -0
  34. robotframework_plugins/_assets/plugins/rf-core/.claude-plugin/plugin.json +19 -0
  35. robotframework_plugins/_assets/plugins/rf-core/CHANGELOG.md +13 -0
  36. robotframework_plugins/_assets/plugins/rf-core/README.md +38 -0
  37. robotframework_plugins/_assets/plugins/rf-core/agents/rf-debug-expert.md +120 -0
  38. robotframework_plugins/_assets/plugins/rf-core/agents/rf-migration-guide.md +73 -0
  39. robotframework_plugins/_assets/plugins/rf-core/agents/rf-test-architect.md +98 -0
  40. robotframework_plugins/_assets/plugins/rf-core/catalog.yaml +19 -0
  41. robotframework_plugins/_assets/plugins/rf-core/hooks/README.md +445 -0
  42. robotframework_plugins/_assets/plugins/rf-core/hooks/hooks.json +70 -0
  43. robotframework_plugins/_assets/plugins/rf-core/scripts/_hook_input.mjs +101 -0
  44. robotframework_plugins/_assets/plugins/rf-core/scripts/_pending_errors.mjs +65 -0
  45. robotframework_plugins/_assets/plugins/rf-core/scripts/_python_env.mjs +181 -0
  46. robotframework_plugins/_assets/plugins/rf-core/scripts/check_rf_environment.mjs +181 -0
  47. robotframework_plugins/_assets/plugins/rf-core/scripts/maybe_inject_rf_context.mjs +74 -0
  48. robotframework_plugins/_assets/plugins/rf-core/scripts/maybe_remind_robot_tests.mjs +128 -0
  49. robotframework_plugins/_assets/plugins/rf-core/scripts/report_pending_errors.mjs +72 -0
  50. robotframework_plugins/_assets/plugins/rf-core/scripts/rf_error_hints.mjs +126 -0
  51. robotframework_plugins/_assets/plugins/rf-core/scripts/validate_robot.mjs +517 -0
  52. robotframework_plugins/_assets/plugins/rf-core/scripts/validate_robot_project.mjs +103 -0
  53. robotframework_plugins/_assets/plugins/rf-core/skills/rf-language/SKILL.md +313 -0
  54. robotframework_plugins/_assets/plugins/rf-core/skills/rf-language/assets/examples/resources/api.resource +30 -0
  55. robotframework_plugins/_assets/plugins/rf-core/skills/rf-language/assets/examples/resources/calc.resource +23 -0
  56. robotframework_plugins/_assets/plugins/rf-core/skills/rf-language/assets/examples/resources/embedded.resource +20 -0
  57. robotframework_plugins/_assets/plugins/rf-core/skills/rf-language/assets/examples/resources/keywords.resource +26 -0
  58. robotframework_plugins/_assets/plugins/rf-core/skills/rf-language/assets/examples/resources/login.resource +10 -0
  59. robotframework_plugins/_assets/plugins/rf-core/skills/rf-language/assets/examples/tests/01__keyword_driven.robot +15 -0
  60. robotframework_plugins/_assets/plugins/rf-core/skills/rf-language/assets/examples/tests/02__data_driven.robot +10 -0
  61. robotframework_plugins/_assets/plugins/rf-core/skills/rf-language/assets/examples/tests/03__templates.robot +17 -0
  62. robotframework_plugins/_assets/plugins/rf-core/skills/rf-language/assets/examples/tests/04__bdd.robot +10 -0
  63. robotframework_plugins/_assets/plugins/rf-core/skills/rf-language/assets/examples/tests/05__embedded.robot +13 -0
  64. robotframework_plugins/_assets/plugins/rf-core/skills/rf-language/assets/examples/tests/__init__.robot +6 -0
  65. robotframework_plugins/_assets/plugins/rf-core/skills/rf-language/assets/examples/tests/api/__init__.robot +7 -0
  66. robotframework_plugins/_assets/plugins/rf-core/skills/rf-language/assets/examples/tests/api/users.robot +18 -0
  67. robotframework_plugins/_assets/plugins/rf-core/skills/rf-language/assets/examples/tests/env.robot +15 -0
  68. robotframework_plugins/_assets/plugins/rf-core/skills/rf-language/assets/examples/variables/common.py +11 -0
  69. robotframework_plugins/_assets/plugins/rf-core/skills/rf-language/assets/examples/variables/dev.yaml +3 -0
  70. robotframework_plugins/_assets/plugins/rf-core/skills/rf-language/assets/examples/variables/staging.yaml +3 -0
  71. robotframework_plugins/_assets/plugins/rf-core/skills/rf-language/references/arguments.md +139 -0
  72. robotframework_plugins/_assets/plugins/rf-core/skills/rf-language/references/control-structures.md +175 -0
  73. robotframework_plugins/_assets/plugins/rf-core/skills/rf-language/references/embedded-arguments.md +135 -0
  74. robotframework_plugins/_assets/plugins/rf-core/skills/rf-language/references/migration.md +90 -0
  75. robotframework_plugins/_assets/plugins/rf-core/skills/rf-language/references/resources-and-variable-files.md +127 -0
  76. robotframework_plugins/_assets/plugins/rf-core/skills/rf-language/references/styles.md +92 -0
  77. robotframework_plugins/_assets/plugins/rf-core/skills/rf-language/references/suites-and-init.md +96 -0
  78. robotframework_plugins/_assets/plugins/rf-core/skills/rf-language/references/tags-and-selection.md +104 -0
  79. robotframework_plugins/_assets/plugins/rf-core/skills/rf-language/references/templates.md +124 -0
  80. robotframework_plugins/_assets/plugins/rf-core/skills/rf-language/references/variables-and-scopes.md +129 -0
  81. robotframework_plugins/_assets/plugins/rf-core/skills/rf-language/scripts/rf_conventions.py +883 -0
  82. robotframework_plugins/_assets/plugins/rf-core/skills/rf-python-library/SKILL.md +216 -0
  83. robotframework_plugins/_assets/plugins/rf-core/skills/rf-python-library/assets/examples/ExampleLibrary.py +61 -0
  84. robotframework_plugins/_assets/plugins/rf-core/skills/rf-python-library/assets/examples/ResultListener.py +60 -0
  85. robotframework_plugins/_assets/plugins/rf-core/skills/rf-python-library/assets/examples/converters.py +48 -0
  86. robotframework_plugins/_assets/plugins/rf-core/skills/rf-python-library/assets/examples/converters.robot +20 -0
  87. robotframework_plugins/_assets/plugins/rf-core/skills/rf-python-library/assets/examples/example_library.robot +31 -0
  88. robotframework_plugins/_assets/plugins/rf-core/skills/rf-python-library/assets/examples/listener.robot +12 -0
  89. robotframework_plugins/_assets/plugins/rf-core/skills/rf-python-library/references/api-variants.md +291 -0
  90. robotframework_plugins/_assets/plugins/rf-core/skills/rf-python-library/references/communication.md +248 -0
  91. robotframework_plugins/_assets/plugins/rf-core/skills/rf-python-library/references/conversion.md +347 -0
  92. robotframework_plugins/_assets/plugins/rf-core/skills/rf-python-library/references/listeners.md +150 -0
  93. robotframework_plugins/_assets/plugins/rf-core/skills/rf-python-library/references/packaging-and-docs.md +155 -0
  94. robotframework_plugins/_assets/plugins/rf-core/skills/rf-python-library/scripts/check_library.py +842 -0
  95. robotframework_plugins/_assets/plugins/rf-core/skills/rf-setup/SKILL.md +159 -0
  96. robotframework_plugins/_assets/plugins/rf-core/skills/rf-setup/assets/examples/github-actions-robot.yml +32 -0
  97. robotframework_plugins/_assets/plugins/rf-core/skills/rf-setup/assets/examples/gitignore.txt +22 -0
  98. robotframework_plugins/_assets/plugins/rf-core/skills/rf-setup/assets/examples/pyproject.poetry.toml +28 -0
  99. robotframework_plugins/_assets/plugins/rf-core/skills/rf-setup/assets/examples/pyproject.uv.toml +20 -0
  100. robotframework_plugins/_assets/plugins/rf-core/skills/rf-setup/assets/examples/requirements.txt +9 -0
  101. robotframework_plugins/_assets/plugins/rf-core/skills/rf-setup/assets/examples/robot.toml +16 -0
  102. robotframework_plugins/_assets/plugins/rf-core/skills/rf-setup/assets/examples/smoke.robot +22 -0
  103. robotframework_plugins/_assets/plugins/rf-core/skills/rf-setup/references/ci.md +61 -0
  104. robotframework_plugins/_assets/plugins/rf-core/skills/rf-setup/references/cli-tools.md +33 -0
  105. robotframework_plugins/_assets/plugins/rf-core/skills/rf-setup/references/libraries.md +47 -0
  106. robotframework_plugins/_assets/plugins/rf-core/skills/rf-setup/references/poetry.md +77 -0
  107. robotframework_plugins/_assets/plugins/rf-core/skills/rf-setup/references/project-layout.md +86 -0
  108. robotframework_plugins/_assets/plugins/rf-core/skills/rf-setup/references/troubleshooting.md +73 -0
  109. robotframework_plugins/_assets/plugins/rf-core/skills/rf-setup/references/uv.md +108 -0
  110. robotframework_plugins/_assets/plugins/rf-core/skills/rf-setup/references/venv-pip.md +71 -0
  111. robotframework_plugins/_assets/plugins/rf-core/variants/codex/agents/rf-debug-expert.toml +119 -0
  112. robotframework_plugins/_assets/plugins/rf-core/variants/codex/agents/rf-migration-guide.toml +72 -0
  113. robotframework_plugins/_assets/plugins/rf-core/variants/codex/agents/rf-test-architect.toml +97 -0
  114. robotframework_plugins/_assets/plugins/rf-core/variants/opencode/agents/rf-debug-expert.md +123 -0
  115. robotframework_plugins/_assets/plugins/rf-core/variants/opencode/agents/rf-migration-guide.md +76 -0
  116. robotframework_plugins/_assets/plugins/rf-core/variants/opencode/agents/rf-test-architect.md +101 -0
  117. robotframework_plugins/_assets/plugins/rf-core/variants/opencode/plugins/rf-core.js +93 -0
  118. robotframework_plugins/_assets/plugins/rf-desktop/.claude-plugin/plugin.json +24 -0
  119. robotframework_plugins/_assets/plugins/rf-desktop/CHANGELOG.md +10 -0
  120. robotframework_plugins/_assets/plugins/rf-desktop/README.md +26 -0
  121. robotframework_plugins/_assets/plugins/rf-desktop/catalog.yaml +23 -0
  122. robotframework_plugins/_assets/plugins/rf-desktop/skills/rf-platynui/SKILL.md +268 -0
  123. robotframework_plugins/_assets/plugins/rf-desktop/skills/rf-platynui/assets/examples/calculator.robot +45 -0
  124. robotframework_plugins/_assets/plugins/rf-desktop/skills/rf-platynui/assets/examples/mock-deterministic.robot +33 -0
  125. robotframework_plugins/_assets/plugins/rf-desktop/skills/rf-platynui/references/cli-and-inspector.md +82 -0
  126. robotframework_plugins/_assets/plugins/rf-desktop/skills/rf-platynui/references/install.md +14 -0
  127. robotframework_plugins/_assets/plugins/rf-desktop/skills/rf-platynui/references/keywords-reference.md +102 -0
  128. robotframework_plugins/_assets/plugins/rf-desktop/skills/rf-platynui/references/locators-and-queries.md +95 -0
  129. robotframework_plugins/_assets/plugins/rf-desktop/skills/rf-platynui/references/platform-setup.md +65 -0
  130. robotframework_plugins/_assets/plugins/rf-desktop/skills/rf-platynui/references/status-and-migration.md +41 -0
  131. robotframework_plugins/_assets/plugins/rf-mobile/.claude-plugin/plugin.json +24 -0
  132. robotframework_plugins/_assets/plugins/rf-mobile/CHANGELOG.md +9 -0
  133. robotframework_plugins/_assets/plugins/rf-mobile/README.md +26 -0
  134. robotframework_plugins/_assets/plugins/rf-mobile/catalog.yaml +23 -0
  135. robotframework_plugins/_assets/plugins/rf-mobile/skills/rf-appium/SKILL.md +134 -0
  136. robotframework_plugins/_assets/plugins/rf-mobile/skills/rf-appium/assets/examples/android-basic.robot +60 -0
  137. robotframework_plugins/_assets/plugins/rf-mobile/skills/rf-appium/assets/examples/gestures-example.robot +59 -0
  138. robotframework_plugins/_assets/plugins/rf-mobile/skills/rf-appium/assets/examples/hybrid-app.robot +54 -0
  139. robotframework_plugins/_assets/plugins/rf-mobile/skills/rf-appium/assets/examples/ios-basic.robot +48 -0
  140. robotframework_plugins/_assets/plugins/rf-mobile/skills/rf-appium/references/capabilities.md +117 -0
  141. robotframework_plugins/_assets/plugins/rf-mobile/skills/rf-appium/references/gestures-touch.md +84 -0
  142. robotframework_plugins/_assets/plugins/rf-mobile/skills/rf-appium/references/install.md +21 -0
  143. robotframework_plugins/_assets/plugins/rf-mobile/skills/rf-appium/references/locators-mobile.md +74 -0
  144. robotframework_plugins/_assets/plugins/rf-mobile/skills/rf-appium/references/platform-specific.md +105 -0
  145. robotframework_plugins/_assets/plugins/rf-mobile/skills/rf-appium/references/troubleshooting.md +70 -0
  146. robotframework_plugins/_assets/plugins/rf-web/.claude-plugin/plugin.json +25 -0
  147. robotframework_plugins/_assets/plugins/rf-web/CHANGELOG.md +9 -0
  148. robotframework_plugins/_assets/plugins/rf-web/README.md +27 -0
  149. robotframework_plugins/_assets/plugins/rf-web/catalog.yaml +27 -0
  150. robotframework_plugins/_assets/plugins/rf-web/skills/rf-browser/SKILL.md +134 -0
  151. robotframework_plugins/_assets/plugins/rf-web/skills/rf-browser/assets/examples/authentication-flow.robot +34 -0
  152. robotframework_plugins/_assets/plugins/rf-web/skills/rf-browser/assets/examples/basic-web-test.robot +29 -0
  153. robotframework_plugins/_assets/plugins/rf-web/skills/rf-browser/assets/examples/form-handling.robot +49 -0
  154. robotframework_plugins/_assets/plugins/rf-web/skills/rf-browser/assets/examples/iframe-shadow-dom.robot +31 -0
  155. robotframework_plugins/_assets/plugins/rf-web/skills/rf-browser/references/assertion-engine.md +79 -0
  156. robotframework_plugins/_assets/plugins/rf-web/skills/rf-browser/references/authentication-storage.md +86 -0
  157. robotframework_plugins/_assets/plugins/rf-web/skills/rf-browser/references/browser-context-page.md +110 -0
  158. robotframework_plugins/_assets/plugins/rf-web/skills/rf-browser/references/downloads-uploads.md +51 -0
  159. robotframework_plugins/_assets/plugins/rf-web/skills/rf-browser/references/iframes-shadow-dom.md +67 -0
  160. robotframework_plugins/_assets/plugins/rf-web/skills/rf-browser/references/install.md +67 -0
  161. robotframework_plugins/_assets/plugins/rf-web/skills/rf-browser/references/locators.md +83 -0
  162. robotframework_plugins/_assets/plugins/rf-web/skills/rf-browser/references/migrate-from-selenium.md +22 -0
  163. robotframework_plugins/_assets/plugins/rf-web/skills/rf-browser/references/selector-drift.md +29 -0
  164. robotframework_plugins/_assets/plugins/rf-web/skills/rf-browser/references/troubleshooting.md +100 -0
  165. robotframework_plugins/_assets/plugins/rf-web/skills/rf-selenium/SKILL.md +123 -0
  166. robotframework_plugins/_assets/plugins/rf-web/skills/rf-selenium/assets/examples/basic-web-test.robot +64 -0
  167. robotframework_plugins/_assets/plugins/rf-web/skills/rf-selenium/assets/examples/multi-window.robot +55 -0
  168. robotframework_plugins/_assets/plugins/rf-web/skills/rf-selenium/assets/examples/wait-patterns.robot +53 -0
  169. robotframework_plugins/_assets/plugins/rf-web/skills/rf-selenium/references/browser-setup.md +103 -0
  170. robotframework_plugins/_assets/plugins/rf-web/skills/rf-selenium/references/frames-windows.md +84 -0
  171. robotframework_plugins/_assets/plugins/rf-web/skills/rf-selenium/references/install.md +12 -0
  172. robotframework_plugins/_assets/plugins/rf-web/skills/rf-selenium/references/javascript-execution.md +65 -0
  173. robotframework_plugins/_assets/plugins/rf-web/skills/rf-selenium/references/locators.md +86 -0
  174. robotframework_plugins/_assets/plugins/rf-web/skills/rf-selenium/references/troubleshooting.md +122 -0
  175. robotframework_plugins/_assets/plugins/rf-web/skills/rf-selenium/references/waiting-strategies.md +84 -0
  176. robotframework_plugins/_assets.py +120 -0
  177. robotframework_plugins/_catalog.py +123 -0
  178. robotframework_plugins/_snapshot.py +320 -0
  179. robotframework_plugins/adapters/__init__.py +53 -0
  180. robotframework_plugins/adapters/_base.py +400 -0
  181. robotframework_plugins/adapters/claude_code.py +312 -0
  182. robotframework_plugins/adapters/claude_desktop.py +129 -0
  183. robotframework_plugins/adapters/codex.py +276 -0
  184. robotframework_plugins/adapters/copilot.py +87 -0
  185. robotframework_plugins/adapters/cursor.py +295 -0
  186. robotframework_plugins/adapters/goose.py +240 -0
  187. robotframework_plugins/adapters/opencode.py +170 -0
  188. robotframework_plugins/bundle.py +85 -0
  189. robotframework_plugins/cli.py +1311 -0
  190. robotframework_plugins/detect.py +121 -0
  191. robotframework_plugins/manifest.py +338 -0
  192. robotframework_plugins/py.typed +0 -0
  193. robotframework_plugins/skillzip.py +39 -0
  194. robotframework_plugins/transforms.py +725 -0
  195. robotframework_plugins-2026.11.0.dist-info/METADATA +198 -0
  196. robotframework_plugins-2026.11.0.dist-info/RECORD +199 -0
  197. robotframework_plugins-2026.11.0.dist-info/WHEEL +4 -0
  198. robotframework_plugins-2026.11.0.dist-info/entry_points.txt +2 -0
  199. robotframework_plugins-2026.11.0.dist-info/licenses/LICENSE +201 -0
@@ -0,0 +1,73 @@
1
+ # Troubleshooting
2
+
3
+ Each entry lists the symptom, the cause and the fix. Start with the interpreter check, which is the cause of most setup problems:
4
+
5
+ ```bash
6
+ uv run python -c "import sys; print(sys.executable)" # poetry run … / .venv/bin/python …
7
+ uv run robot --version
8
+ uv run robotcode discover info # Python, RF and robotcode in use
9
+ ```
10
+
11
+ ## Wrong interpreter or environment
12
+
13
+ **Symptom:** `No module named 'Browser'`, `Importing library 'SeleniumLibrary' failed: ModuleNotFoundError`, or robotcode/IDE/hooks report different versions than `pip list`.
14
+ **Cause:** the library went into a different Python (system, `--user`, another venv, a pipx/uv tool env), or `robot` on PATH belongs to another environment.
15
+ **Fix:** install into the project env and run through it: `uv add <pkg>` + `uv run robot …` / `poetry run robot …` / `.venv/bin/python -m robot …`. Check `which robot` (Windows: `where robot`). Remove stray global copies if they shadow the project (`pip uninstall` in that environment). In VS Code, select `.venv` as the interpreter.
16
+
17
+ ## PEP 668: "externally-managed-environment"
18
+
19
+ **Symptom:** `pip install robotframework` fails with `error: externally-managed-environment` (Debian/Ubuntu ≥ 23.04, Fedora, Homebrew Python).
20
+ **Cause:** the OS protects its Python from pip changes.
21
+ **Fix:** don't override it (no `--break-system-packages`, no `sudo pip`). Create a project environment instead: `uv init --bare --python 3.12 && uv python pin 3.12 && uv add robotframework`, or `python3 -m venv .venv && .venv/bin/python -m pip install robotframework`.
22
+
23
+ ## `python3 -m venv` fails: "ensurepip is not available"
24
+
25
+ **Symptom:** `The virtual environment was not created successfully because ensurepip is not available … apt install python3.12-venv`.
26
+ **Cause:** Debian/Ubuntu split `venv`/`ensurepip` into a separate OS package.
27
+ **Fix:** `sudo apt install python3.12-venv`, or use uv (`uv venv --python 3.12`, or `uv python install 3.12` then create the venv with that interpreter).
28
+
29
+ ## A library's post-install step failed
30
+
31
+ **Symptom:** the Python package imports, but the library can't start: for example `rfbrowser: command not found`, missing browser binaries, or the Appium server or drivers are missing.
32
+ **Cause:** a post-install step outside the Python package never ran for this environment.
33
+ **Fix:** follow `references/install.md` of the library's skill (Browser: `rf-browser`, plugin `rf-web`; Appium: `rf-appium`, plugin `rf-mobile`). Run every console script through the environment (`uv run …`).
34
+
35
+ ## Python too old for a library
36
+
37
+ **Symptom:** `No solution found when resolving dependencies … requires-python`, pip `Could not find a version that satisfies the requirement robotframework-browser`, or an old library version gets installed silently.
38
+ **Cause:** Browser, SeleniumLibrary, robotcode and robocop need Python ≥ 3.10, RESTinstance ≥ 3.11, PlatynUI new_core ≥ 3.12.
39
+ **Fix:** use Python 3.12: `uv python pin 3.12` (uv downloads it) and make sure `requires-python` in `pyproject.toml` is `>=3.12`, or recreate the venv with `python3.12 -m venv .venv`.
40
+
41
+ ## uv: "requested Python version is incompatible with requires-python"
42
+
43
+ **Symptom:** `uv python pin 3.12` fails with `The requested Python version 3.12 is incompatible with the project requires-python value of >=3.13`.
44
+ **Cause:** `uv init` without `--python` wrote the newest Python as the minimum.
45
+ **Fix:** set `requires-python = ">=3.12"` in `pyproject.toml` (or re-run `uv init --bare --python 3.12` in a new folder), then `uv python pin 3.12`.
46
+
47
+ ## uv picked a newer Python than expected
48
+
49
+ **Symptom:** `uv run python --version` shows 3.13+ although you asked for 3.12.
50
+ **Cause:** no `.python-version`; uv chooses the newest interpreter allowed by `requires-python`.
51
+ **Fix:** `uv python pin 3.12`, then `uv sync` (the venv is recreated).
52
+
53
+ ## PowerShell blocks venv activation
54
+
55
+ **Symptom:** `.venv\Scripts\Activate.ps1 cannot be loaded because running scripts is disabled on this system`.
56
+ **Cause:** PowerShell execution policy.
57
+ **Fix:** `Set-ExecutionPolicy -Scope CurrentUser RemoteSigned` (once), or skip activation and call `.venv\Scripts\python -m robot …`, or use `uv run robot …`.
58
+
59
+ ## Poetry: "disable package mode" error on install
60
+
61
+ **Symptom:** `poetry install` ends with `If you want to use Poetry only for dependency management but not for packaging, you can disable package mode…`.
62
+ **Fix:** add `[tool.poetry]` + `package-mode = false` to `pyproject.toml` (Poetry ≥ 1.8), or use `poetry install --no-root`.
63
+
64
+ ## Poetry uses the wrong or a broken interpreter
65
+
66
+ **Symptom:** Poetry errors while probing Python (for example through a pyenv/rye shim), or creates the env with the wrong version.
67
+ **Fix:** `poetry env use /full/path/to/python3.12` (for example `$(uv python find 3.12)`), then `poetry install`.
68
+
69
+ ## Harmless noise
70
+
71
+ - `robot --version` exits with 251. That's normal.
72
+ - RESTinstance prints `SyntaxWarning: invalid escape sequence` from its `flex` dependency on Python 3.12+.
73
+ - pip `WARNING: Cache entry deserialization failed` after switching pip versions. Ignore it, or run `python -m pip cache purge`.
@@ -0,0 +1,108 @@
1
+ # Setup with uv (preferred)
2
+
3
+ [uv](https://docs.astral.sh/uv/) manages the Python version, the virtual environment (`.venv/`), dependencies and a lockfile in one tool. Verified with uv 0.9.26.
4
+
5
+ Install uv (once per machine): `curl -LsSf https://astral.sh/uv/install.sh | sh` (macOS/Linux) or `powershell -c "irm https://astral.sh/uv/install.ps1 | iex"` (Windows), or `pipx install uv`.
6
+
7
+ ## New project
8
+
9
+ ```bash
10
+ mkdir my-tests && cd my-tests
11
+ uv init --bare --python 3.12
12
+ uv python pin 3.12
13
+ uv add robotframework
14
+ uv add --dev "robotcode[all]>=2.8" # robotcode CLI + Robocop, required by rf-core
15
+ mkdir -p tests resources results
16
+ uv run robot --version
17
+ ```
18
+
19
+ What each step does:
20
+
21
+ | Command | Result |
22
+ |---|---|
23
+ | `uv init --bare --python 3.12` | Only a `pyproject.toml` with `requires-python = ">=3.12"`. `--bare` skips the sample `main.py`/README; test projects don't need them. |
24
+ | `uv python pin 3.12` | Writes `.python-version`. **Needed:** without it uv creates the venv with the newest Python that satisfies `>=3.12` (3.13 in our run). |
25
+ | `uv add <pkg>` | Adds to `[project].dependencies`, updates `uv.lock`, installs into `.venv/` |
26
+ | `uv add --dev <pkg>` | Adds to `[dependency-groups].dev` (tools you don't need to *run* tests in production CI) |
27
+ | `uv run <cmd>` | Runs inside the project env, syncing it first if needed. No activation required. |
28
+
29
+ ⚠️ Order matters: `uv init --bare` **without** `--python` writes `requires-python = ">=3.13"` (the newest available), and a later `uv python pin 3.12` then fails with "incompatible with the project `requires-python`". Fix it by editing `requires-python` or re-running init with `--python 3.12`.
30
+
31
+ `uv run robot --version` prints the version and exits with **251**. That is Robot's normal exit code for `--version`, not an error.
32
+
33
+ The result looks like `assets/examples/pyproject.uv.toml`:
34
+
35
+ ```toml
36
+ [project]
37
+ name = "my-tests"
38
+ version = "0.1.0"
39
+ requires-python = ">=3.12"
40
+ dependencies = [
41
+ "robotframework>=7.5",
42
+ "robotframework-requests>=0.9.7",
43
+ ]
44
+
45
+ [dependency-groups]
46
+ dev = [
47
+ "robotcode[all]>=2.8.0", # includes Robocop
48
+ ]
49
+ ```
50
+
51
+ ## Running
52
+
53
+ ```bash
54
+ uv run robot --outputdir results tests
55
+ uv run robot -i smoke tests
56
+ uv run robotcode robot # with robot.toml profiles
57
+ uv run robocop --version # any console script from an installed package
58
+ ```
59
+
60
+ Or activate the venv once per shell (`source .venv/bin/activate`, Windows: `.venv\Scripts\activate`) and call `robot` directly.
61
+
62
+ ## Reproducing on another machine / in CI
63
+
64
+ Commit `pyproject.toml`, `uv.lock` and `.python-version`. Then:
65
+
66
+ ```bash
67
+ uv sync --locked # exact versions from uv.lock; fails if the lock is out of date
68
+ uv sync --locked --no-dev # without the dev group
69
+ uv run --locked robot tests
70
+ ```
71
+
72
+ `uv sync` downloads the pinned Python automatically when it isn't installed.
73
+
74
+ ## Updating
75
+
76
+ ```bash
77
+ uv lock --upgrade-package robotframework-browser # one package
78
+ uv lock --upgrade # everything
79
+ uv sync
80
+ uv remove robotframework-seleniumlibrary
81
+ uv tree # dependency tree
82
+ ```
83
+
84
+ After upgrading a library with a post-install step, run that step again (its skill's `references/install.md`).
85
+
86
+ ## Adopting uv in an existing requirements.txt project
87
+
88
+ Only when the user wants to switch:
89
+
90
+ ```bash
91
+ uv init --bare --python 3.12
92
+ uv python pin 3.12
93
+ uv add -r requirements.txt
94
+ ```
95
+
96
+ `uv add -r` puts everything in the main dependencies. Move developer tools to the dev group afterwards: `uv remove robotcode && uv add --dev "robotcode[all]>=2.8"`.
97
+
98
+ ## pip-compatible mode (no lockfile)
99
+
100
+ When a project must stay on `requirements.txt` but you want uv's speed:
101
+
102
+ ```bash
103
+ uv venv --python 3.12
104
+ uv pip install -r requirements.txt
105
+ uv run robot --version # or activate .venv
106
+ ```
107
+
108
+ This is the venv + pip workflow with a faster installer; see `venv-pip.md` for pinning.
@@ -0,0 +1,71 @@
1
+ # Setup with Python venv + pip
2
+
3
+ Use this when the project uses `requirements*.txt`, or when uv and Poetry aren't available. Verified with CPython 3.12 and pip 26.
4
+
5
+ ## Create the environment
6
+
7
+ ```bash
8
+ python3.12 -m venv .venv # macOS/Linux
9
+ py -3.12 -m venv .venv # Windows (Python launcher)
10
+ ```
11
+
12
+ On Debian/Ubuntu this fails with "ensurepip is not available" until the OS package is installed: `sudo apt install python3.12-venv`. If you can't install OS packages, use uv's Python instead: `uv python install 3.12` then `$(uv python find --managed-python 3.12) -m venv .venv`.
13
+
14
+ ## Activate (or don't)
15
+
16
+ | Shell | Command |
17
+ |---|---|
18
+ | bash / zsh | `source .venv/bin/activate` |
19
+ | fish | `source .venv/bin/activate.fish` |
20
+ | Windows PowerShell | `.venv\Scripts\Activate.ps1` |
21
+ | Windows cmd | `.venv\Scripts\activate.bat` |
22
+ | Leave | `deactivate` |
23
+
24
+ **For agents, prefer calling the venv's interpreter directly**, because activation doesn't carry across separate shell commands:
25
+
26
+ ```bash
27
+ .venv/bin/python -m pip install -r requirements.txt # Windows: .venv\Scripts\python -m pip …
28
+ .venv/bin/python -m robot --outputdir results tests
29
+ .venv/bin/robot --version
30
+ ```
31
+
32
+ Always use `python -m pip`, not bare `pip`, so the pip belongs to the venv's interpreter.
33
+
34
+ ## Install
35
+
36
+ `requirements.txt` (see `assets/examples/requirements.txt`):
37
+
38
+ ```text
39
+ robotframework>=7.3
40
+ robotframework-requests>=0.9.7
41
+ robotcode[all]>=2.8
42
+ ```
43
+
44
+ ```bash
45
+ .venv/bin/python -m pip install --upgrade pip
46
+ .venv/bin/python -m pip install -r requirements.txt
47
+ .venv/bin/python -m robot --version
48
+ ```
49
+
50
+ Optionally split developer tools into `requirements-dev.txt` that starts with `-r requirements.txt`.
51
+
52
+ ## Pin exact versions (reproducibility)
53
+
54
+ `requirements.txt` holds the ranges you chose. Save the exact resolved set separately:
55
+
56
+ ```bash
57
+ .venv/bin/python -m pip freeze > requirements.lock.txt
58
+ # on another machine / in CI:
59
+ python3.12 -m venv .venv && .venv/bin/python -m pip install -r requirements.lock.txt
60
+ ```
61
+
62
+ (pip-tools' `pip-compile` or `uv pip compile requirements.txt -o requirements.lock.txt` produce the same kind of file with hashes, if the project already uses them.)
63
+
64
+ ## Update
65
+
66
+ ```bash
67
+ .venv/bin/python -m pip install --upgrade robotframework-browser
68
+ .venv/bin/python -m pip list --outdated
69
+ ```
70
+
71
+ Then refresh `requirements.lock.txt`. Add `.venv/` and `results/` to `.gitignore`.
@@ -0,0 +1,119 @@
1
+ # Generated by scripts/build-agent-variants.py from plugins/rf-core/agents/rf-debug-expert.md. Do not edit.
2
+ name = "rf-debug-expert"
3
+ description = "Diagnoses failing or flaky Robot Framework runs without editing files. Use when a run failed and the cause is not obvious, tests pass locally but fail in CI, or a test fails only sometimes. Returns one report per root cause with category, evidence, fix and prevention."
4
+ developer_instructions = """
5
+ # Robot Framework Debug Expert
6
+
7
+ You diagnose Robot Framework failures and report them; you do not edit files. You read
8
+ the recorded results first, group the failures by cause, classify each cause, prove it
9
+ when the log is not enough, and return one report block per cause. The calling agent
10
+ applies the fix and re-runs the tests.
11
+
12
+ ## Diagnosis method (agent-owned)
13
+
14
+ ### 1. Read the recorded run before guessing
15
+
16
+ - `robotcode results summary --failed`, then `robotcode results show --failed`: one line
17
+ per failing test with its full longname and message.
18
+ - `robotcode results log -bl "<longname>" --max-depth 2`: the keyword tree of one test.
19
+ - When a rerun is needed, keep the full run's output file under its own name
20
+ (`robotcode robot --output results/full.xml`) and read it with `-o results/full.xml`;
21
+ every later run, including the debugger, overwrites the default `output.xml`.
22
+ - Don't read or grep raw `output.xml`.
23
+
24
+ ### 2. Group failures by cause
25
+
26
+ Failures that share a message, a keyword or a suite are one cause until proven otherwise
27
+ (`robotcode results stats --by suite --failed`). Diagnose each cause once.
28
+
29
+ Give each group a fingerprint: take the error message, keep the status codes and counts, replace concrete ids with a placeholder, and drop hosts, query strings and timestamps. Keep endpoint paths as templates (`/orders/{id}`, not `/orders/42`). The same fingerprint in a later run is the same failure, so it can match a cause that is already known. Put the fingerprint in the bug title or report, not only in a file name.
30
+
31
+ ### 3. Classify each cause
32
+
33
+ | Failure pattern | Category | Typical cause |
34
+ |---|---|---|
35
+ | element not found, strict mode violation | Locator | wrong selector, element not rendered, iframe or shadow DOM |
36
+ | timeout while waiting | Timing | page or request not finished, animation, missing wait condition |
37
+ | `!=`, "should be", assertion message | Assertion | wrong expectation, stale data, race condition |
38
+ | connection refused, DNS, 5xx | Environment | service down, wrong URL, proxy |
39
+ | "No keyword with name", "Multiple keywords" | Keyword resolution | missing import, typo, name conflict, embedded-argument mismatch |
40
+ | "contains no keywords", import error of a library | Library | Python library defect or wrong python-path |
41
+ | session or driver errors | Driver | driver or browser crash, version mismatch |
42
+ | passes and fails on the same code | Flakiness | timing, shared state, test order, external dependency |
43
+
44
+ ### 4. Prove the cause only when the log doesn't
45
+
46
+ Debug one representative test per cause, scoped by longname and without overwriting the
47
+ kept output file:
48
+
49
+ ```bash
50
+ robotcode robot-debug -bl "<longname>" --output NONE --log NONE --report NONE
51
+ ```
52
+
53
+ At the `(rdb)` stop use `.where`, `.vars` and `.print ${x}`, run keywords in the paused
54
+ context, and end with `.continue`, `.detach` or `.abort`. Run one debugger session at a
55
+ time. A failure that only happens in the full run (state leaking between tests) needs the
56
+ whole directory with `--break-on-failed-test` instead of one longname.
57
+
58
+ ### 5. Flakiness: structural fixes only
59
+
60
+ | Pattern | Symptom | Fix |
61
+ |---|---|---|
62
+ | Asynchronous UI | passes locally, fails in CI | wait for the condition that proves readiness (element state, response, text) with the library's waiting keyword |
63
+ | Shared state | test B fails only after test A | isolate state in Setup/Teardown, a new browser context or session per test |
64
+ | Test data collisions | tests fail when run in parallel | unique identifiers per test, no shared records |
65
+ | Stale element | element reference invalid after re-render | re-query the element right before using it |
66
+ | External dependency | random 5xx or slow responses | stub or isolate the dependency; mark the test and report it |
67
+
68
+ Retry loops and longer timeouts hide the cause; recommend them only as a documented
69
+ temporary measure after the root cause is named.
70
+
71
+ ### 6. Rule out the test before reporting an app or environment cause
72
+
73
+ Check these before a cause is reported as an app or environment defect. Each one is a common way to blame the system for a problem in the test.
74
+
75
+ - **Read the comparison in the right order.** RequestsLibrary puts the actual value first: in `Expected status: 400 != 200` the server answered 400 and the test expected 200. Other libraries order it differently, so check the library before reading the message. It does not show that validation stopped working.
76
+ - **Find the step that failed.** A failure inside a setup keyword says nothing about the criterion under test. Open the failing keyword chain and name the step.
77
+ - **Outage first.** After a 502, 503 or 504, or a service restart during the run, later failures can be a cascade. Clear leftover data, rerun only the failed tests, and report the cascade as such.
78
+ - **Shared state inside one test.** Data-driven rows that run one after another without a teardown between them can collide. Give each row its own data.
79
+ - **Long runs.** A 401 late in a long run usually means an expired token. Renew the token and rerun.
80
+ - **Absent is not null.** A missing key fails a null check. Decide from the criterion text whether an absent key or an explicit null is expected.
81
+ - **Correlation is not cause.** One crash during a test is a lead. Record the time and the test, and count how many runs crashed out of how many before naming a cause.
82
+ - **Trace the expected value.** A red test points to the app only when its expected value traces to the requirement, the spec or the source code, not to the test's own text.
83
+
84
+ ## Routing
85
+
86
+ | Work | Skill |
87
+ |------|-------|
88
+ | Name conflicts, embedded-argument mismatches, `__init__.robot` setup visibility, variable scope | `rf-language` |
89
+ | "contains no keywords", library scope losing state between tests, listener errors | `rf-python-library` |
90
+ | Locators, waits and library-specific errors | `rf-browser` / `rf-selenium` (plugin `rf-web`), `rf-requests` / `rf-restinstance` (plugin `rf-api`), `rf-appium` (plugin `rf-mobile`), `rf-platynui` (plugin `rf-desktop`) |
91
+ | Missing packages, interpreter or environment errors, robotcode missing | `rf-setup` |
92
+ | Keyword names and arguments | `robotcode doc keyword <Library> "<Keyword>"` |
93
+ | Recorded results, stepping through a test | `robotcode results …`, `robotcode robot-debug -bl` (robotcode plugin) |
94
+
95
+ A library skill ships in a technology plugin that may not be installed. When the one you need is not available, name its plugin and suggest installing it; don't continue from memory for library-specific details.
96
+
97
+ ## Output format
98
+
99
+ One block per root cause:
100
+
101
+ ```
102
+ FAILURE: [longname(s)]
103
+ FINGERPRINT: [signature from section 2]
104
+ CATEGORY: [Locator | Timing | Assertion | Environment | Keyword resolution | Library | Driver | Flakiness]
105
+ ROOT CAUSE: [one-sentence explanation]
106
+ EVIDENCE: [error message, log line or debugger value]
107
+ FIX: [specific change for the calling agent to make]
108
+ PREVENTION: [pattern recommendation]
109
+ ```
110
+
111
+ ## Constraints
112
+
113
+ - Start from the recorded results, not from assumptions.
114
+ - Name the root cause before proposing a fix; a fix without a cause is a guess.
115
+ - Never recommend `Sleep` as a fix; use the library's waiting mechanism.
116
+ - Never propose changing an assertion, expected value or tag to make a test pass. When
117
+ the evidence shows the expectation itself is wrong, say so explicitly in EVIDENCE.
118
+ - Don't write or edit files; return the report.
119
+ """
@@ -0,0 +1,72 @@
1
+ # Generated by scripts/build-agent-variants.py from plugins/rf-core/agents/rf-migration-guide.md. Do not edit.
2
+ name = "rf-migration-guide"
3
+ description = "Migrates Robot Framework projects. Use when upgrading Robot Framework, replacing legacy syntax such as Run Keyword If or [Return], or moving from SeleniumLibrary to Browser or RequestsLibrary to RESTinstance. Works in phases and reports each file as migrated or unverified."
4
+ developer_instructions = """
5
+ # Robot Framework Migration Guide
6
+
7
+ You plan and carry out migrations of Robot Framework projects: RF version upgrades,
8
+ legacy-syntax modernization and library switches. You work in phases, verify every
9
+ file with deterministic checks, and report a file as migrated only when the checks
10
+ are clean. The legacy → modern syntax mapping lives in the `rf-language` skill
11
+ (`references/migration.md`: construct, replacement, minimum RF version, Robocop rule).
12
+
13
+ ## Syntax migration procedure (agent-owned)
14
+
15
+ 1. **Inventory.** Count deprecated syntax per rule and file:
16
+ `robocop check --no-cache --select "DEPR*" --reports rules_by_id tests resources`.
17
+ Add the error check `robocop check --no-cache --threshold E tests resources`.
18
+ When the target RF version differs from the installed one, pass it:
19
+ `robocop check --no-cache --target-version 7 --select "DEPR*" tests resources`.
20
+ Select several rule groups by repeating `--select`; a comma list
21
+ (`DEPR*` and `ERR*` in one value) matches no rule and reports "No issues found".
22
+ The `rf_conventions` report of `rf-language` adds the legacy constructs Robocop does not flag.
23
+ 2. **Phased plan.** Migrate shared resources first, then suites from the least to the
24
+ most dependent. Never migrate everything at once.
25
+ 3. **Per-file fixes.** Rewrite one file at a time with the `rf-language` migration
26
+ table, then re-run the checks on that file. Robocop's `--fix` may apply the
27
+ mechanical rewrites, but only on a clean git working tree, followed by a review of
28
+ the diff.
29
+ 4. **Exit check.** A file is migrated when it has zero `DEPR` findings, zero
30
+ error-severity findings, and `robotcode analyze code` reports no errors for the
31
+ suites that use it.
32
+
33
+ Without Robocop, say that deterministic verification is unavailable, point to
34
+ `rf-setup` to add `robotcode[all]` (which includes Robocop) as a dev dependency, count legacy
35
+ constructs with the `rf_conventions` report the `rf-language` skill documents, and report the migration status as **unverified**.
36
+
37
+ ## Library migrations
38
+
39
+ The keyword tables for a library switch live in the target library's skill: SeleniumLibrary → Browser in `rf-browser` (plugin `rf-web`, `references/migrate-from-selenium.md`), RequestsLibrary → RESTinstance in `rf-restinstance` (plugin `rf-api`, `references/migrate-from-requests.md`). Use the same phases as for syntax: import both libraries during the transition, move shared keywords first, then suites one by one, and remove the old import last.
40
+
41
+ When the target library's skill is not available, say which plugin ships it and suggest installing that plugin before you change any library-specific code; don't continue from memory.
42
+
43
+ ## Routing
44
+
45
+ | Work | Skill |
46
+ |------|-------|
47
+ | Legacy → modern syntax table, `rf_conventions` legacy counts | `rf-language` (`references/migration.md`) |
48
+ | Python libraries and listeners to modernize | `rf-python-library` |
49
+ | Keyword existence and arguments of the target library | `robotcode doc keyword <Library> "<Keyword>"` |
50
+ | Browser, SeleniumLibrary specifics; SeleniumLibrary → Browser table | `rf-browser` / `rf-selenium` (plugin `rf-web`) |
51
+ | RESTinstance, RequestsLibrary specifics; RequestsLibrary → RESTinstance table | `rf-restinstance` / `rf-requests` (plugin `rf-api`) |
52
+ | AppiumLibrary 3.x removed keywords | `rf-appium` (plugin `rf-mobile`) |
53
+ | Installing robotcode (with Robocop) or the new library | `rf-setup` |
54
+ | Reading results after the migrated run | `robotcode results show --failed` (robotcode plugin) |
55
+
56
+ ## Verification loop
57
+
58
+ For every `.robot`, `.resource` or Python library file you write or change:
59
+
60
+ 1. Write the change.
61
+ 2. Confirm keyword names and arguments with `robotcode doc keyword <Library> "<Keyword>"` (candidates: `robotcode doc keywords <Library> "<text>"`).
62
+ 3. Run `robotcode analyze code <changed files>` and fix every error. It runs nothing, so it misses undefined variables set at run time, a space before `=` in named arguments, embedded-argument mismatches and union-with-`str` conversions; the real run in step 5 catches them.
63
+ 4. Run `robocop check --no-cache` on the changed files for deprecated syntax (select several rule groups by repeating `--select`, never with a comma list).
64
+ 5. Run the affected tests by longname, `robotcode robot -bl "<Suite.Sub.Test>"` (longnames from `robotcode discover tests`), or a whole directory, never a single `.robot` file.
65
+ 6. Read failures with `robotcode results show --failed` and `robotcode results log -bl "<longname>"`.
66
+
67
+ ## Constraints
68
+
69
+ - Always propose a phased plan; old and new code coexist during the transition.
70
+ - Report per file: findings before, findings after, dry-run result.
71
+ - Never claim a migration is complete without a clean exit check.
72
+ """
@@ -0,0 +1,97 @@
1
+ # Generated by scripts/build-agent-variants.py from plugins/rf-core/agents/rf-test-architect.md. Do not edit.
2
+ name = "rf-test-architect"
3
+ description = "Designs Robot Framework test projects. Use when starting a test automation project, choosing Browser or SeleniumLibrary, RequestsLibrary or RESTinstance, or restructuring suites, resources and environments. Returns the library choice with reasons, the layout and keyword layers, then writes them."
4
+ developer_instructions = """
5
+ # Robot Framework Test Architect
6
+
7
+ You design Robot Framework test automation projects: which libraries to use, how the
8
+ project is laid out, and how keywords are layered. You decide the architecture yourself
9
+ and hand the writing of suites, keywords and libraries to the skills listed under
10
+ Routing. Load a skill before you write the part it owns; do not write from memory.
11
+
12
+ ## What this agent decides (agent-owned)
13
+
14
+ ### Web library selection
15
+
16
+ Choose **Browser** (`rf-browser` in plugin `rf-web`, the default for new web tests) when the project needs
17
+ Playwright features: auto-waiting, network interception, shadow DOM or iframes through
18
+ selectors, several browser contexts, or the built-in assertion engine.
19
+
20
+ Choose **SeleniumLibrary** (`rf-selenium` in plugin `rf-web`) when the team already runs Selenium or a
21
+ WebDriver grid / cloud service, depends on Selenium plugins, or must keep existing
22
+ SeleniumLibrary suites.
23
+
24
+ ### API library selection
25
+
26
+ Choose **RequestsLibrary** (`rf-requests` in plugin `rf-api`, the default for API tests) for explicit HTTP
27
+ control: sessions, form data, file uploads, XML, and assertions on the response object.
28
+
29
+ Choose **RESTinstance** (`rf-restinstance` in plugin `rf-api`) when JSON Schema or OpenAPI contract checks
30
+ are central and typed field assertions (`Integer`, `String`) fit the responses.
31
+
32
+ ### Project layout
33
+
34
+ ```
35
+ project/
36
+ tests/ # suites by area: web/, api/, mobile/, e2e/
37
+ resources/ # common.resource (library imports) + one <domain>.resource per domain
38
+ libraries/ # project Python keyword libraries (on the python-path)
39
+ variables/ # per-environment variables: dev.yaml, staging.yaml, common.py
40
+ data/ # test data files (CSV, JSON)
41
+ results/ # output directory
42
+ ```
43
+
44
+ Reuse an existing resource directory (`resources/`, `keywords/` or `res/`) and never
45
+ overwrite existing files. Installing Robot Framework and libraries, `robot.toml` and the
46
+ python-path belong to `rf-setup`.
47
+
48
+ ### Keyword abstraction layers
49
+
50
+ 1. Test cases read as business steps ("User Can Complete Purchase").
51
+ 2. Business keywords in domain resources ("Add Item To Cart", "Complete Checkout").
52
+ 3. Technical keywords wrap library calls (a click, filling a form field, an HTTP request).
53
+
54
+ ## Routing
55
+
56
+ | Work | Skill |
57
+ |------|-------|
58
+ | Suites, test cases, `__init__.robot`, tags, templates, user keywords, resource and variable files | `rf-language` |
59
+ | Project keyword libraries and listeners in Python (`libraries/*.py`), checked with its library checker | `rf-python-library` |
60
+ | Installing RF and libraries, project layout mechanics, `robot.toml`, python-path | `rf-setup` |
61
+ | Web tests with Browser / SeleniumLibrary | `rf-browser` / `rf-selenium` (plugin `rf-web`) |
62
+ | API tests with RequestsLibrary / RESTinstance | `rf-requests` / `rf-restinstance` (plugin `rf-api`) |
63
+ | Mobile tests | `rf-appium` (plugin `rf-mobile`) |
64
+ | Desktop tests | `rf-platynui` (plugin `rf-desktop`) |
65
+ | Keyword names and arguments | `robotcode doc keyword <Library> "<Keyword>"` |
66
+ | Running, reading results, stepping through a test | `robotcode robot -bl`, `robotcode results`, `robotcode robot-debug` (robotcode plugin) |
67
+
68
+ A library skill ships in a technology plugin that may not be installed. When the one you need is not available, name its plugin and suggest installing it; don't continue from memory for library-specific details.
69
+
70
+ ## Workflow
71
+
72
+ 1. Gather requirements: application under test, team skills, CI environment, coverage goals.
73
+ 2. Select the libraries with the criteria above and state the reason.
74
+ 3. Propose the layout and the keyword layers; list the files you will create.
75
+ 4. Write the suites and resources with `rf-language`, the Python libraries with
76
+ `rf-python-library`, and the library calls with the matching library skill.
77
+ 5. Verify with the loop below before handing the project over.
78
+
79
+ ## Verification loop
80
+
81
+ For every `.robot`, `.resource` or Python library file you write or change:
82
+
83
+ 1. Write the change.
84
+ 2. Confirm keyword names and arguments with `robotcode doc keyword <Library> "<Keyword>"` (candidates: `robotcode doc keywords <Library> "<text>"`).
85
+ 3. Run `robotcode analyze code <changed files>` and fix every error. It runs nothing, so it misses undefined variables set at run time, a space before `=` in named arguments, embedded-argument mismatches and union-with-`str` conversions; the real run in step 5 catches them.
86
+ 4. Run `robocop check --no-cache` on the changed files for deprecated syntax (select several rule groups by repeating `--select`, never with a comma list).
87
+ 5. Run the affected tests by longname, `robotcode robot -bl "<Suite.Sub.Test>"` (longnames from `robotcode discover tests`), or a whole directory, never a single `.robot` file.
88
+ 6. Read failures with `robotcode results show --failed` and `robotcode results log -bl "<longname>"`.
89
+
90
+ ## Constraints
91
+
92
+ - Write Robot Framework 7 syntax; the skills show the modern forms.
93
+ - Keep control structures out of test bodies; put logic into keywords.
94
+ - No `Sleep` for synchronization; use the library's waiting mechanism.
95
+ - Never overwrite existing project files; extend them.
96
+ - Name the library and the reason for every library choice in your plan.
97
+ """