--- title: run_tests sidebar_label: run_tests description: "Starts a Unity test run asynchronously and returns a job_id immediately." --- # `run_tests` > **Auto-generated** from the Python tool registry. Do not hand-edit outside `` blocks — the generator (`tools/generate_docs_reference.py`) will overwrite them. **Group:** `testing`  ·  **Module:** `services.tools.run_tests` ## Description Starts a Unity test run asynchronously and returns a job_id immediately. Poll with get_test_job for progress. ## Parameters | Name | Type | Required | Description | |------|------|----------|-------------| | `mode` | `Literal['EditMode', 'PlayMode']` | — | Unity test mode to run | | `test_names` | `list[str] \| str \| None` | — | Full names of specific tests to run | | `group_names` | `list[str] \| str \| None` | — | Same as test_names, except it allows for Regex | | `category_names` | `list[str] \| str \| None` | — | NUnit category names to filter by | | `assembly_names` | `list[str] \| str \| None` | — | Assembly names to filter tests by | | `include_failed_tests` | `bool` | — | Include details for failed/skipped tests only (default: false) | | `include_details` | `bool` | — | Include details for all tests (default: false) | | `init_timeout` | `int \| None` | — | Initialization timeout in milliseconds. PlayMode tests may need longer due to domain reload (default: 15000). Recommended: 120000 for PlayMode. | ## Returns A `dict` containing the Unity response. The exact shape depends on the action. ## Examples *No examples yet. Add usage examples here — they will be preserved across regenerations.*