run_test_suite
Execute or validate Robot Framework test suites using dry-run, validate, or full execution modes. Manage sessions and suite files for flexible automation testing.
Instructions
Validate or execute a Robot Framework suite.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| mode | No | "dry"/"validate" for dry run; "full" to execute. Defaults to "full". | full |
| session_id | No | Session containing steps to build/execute; optional if suite_file_path is given. | |
| output_level | No | Response verbosity ("minimal", "standard", "detailed"). | standard |
| suite_file_path | No | Path to an existing .robot file to validate/execute. | |
| include_warnings | No | Whether to include warnings in validation output. | |
| validation_level | No | Dry-run validation depth ("minimal", "standard", "strict"). Default "standard". | standard |
| execution_options | No | RF execution options (variables, tags, loglevel, etc.). For ``suite_file_path`` with dry/validate mode, these are forwarded to Robot (e.g. ``variables``, ``include_tags``, ``exclude_tags``, ``test`` / ``tests``, ``pythonpath``, ``loglevel``). Subprocess cap: ``dry_run_timeout`` (preferred), ``dryrun_timeout``, or ``timeout`` (seconds); default comes from config ``DRY_RUN_TIMEOUT``. | |
| capture_screenshots | No | Enable screenshot capture on failures (if supported). |
Output Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||