CLI Options
pytest-f3ts adds an f3ts option group to pytest. Load the plugin with -p f3ts and pass any of these. Running locally you usually need none of them — the defaults run a local plan. The FixturFab Test Runner sets most of them for you when it launches a plan.
| Option | Default | Purpose |
|---|---|---|
--f3ts_config | config.yml | Path to the test-plan config file. See config.yml Schema. |
--test_name | (none) | Test name, used as the stem for the generated log filename. |
--run_id | DEV | Backend run ID to send results to. Stays DEV offline. |
--plan_id | DEV | Backend plan ID to fetch configuration from (when a backend is connected). |
--slot_id | 1 | Fixture slot ID — selects the matching fixture_settings entry and labels results for multi-up fixtures. |
--frontend_client_id | backend | Runner websocket client ID the plugin pushes live updates to. |
--serial_number | (none) | Serial number of the device under test (DUT). |
--backend_url | (none) | Backend REST API base URL (e.g. https://backend:8888/api/v1). When unset, the plugin runs offline. |
--fixture_url | http://localhost:8886 | Fixture API base URL. |
--log_file | (none) | Base log filename stem (without extension) for the run. |
--teardown | off | Flag. Teardown mode — skips registering the reporter plugin. |
--skip-summary | off | Flag. Skip the offline end-of-run summary table (see Running Locally). |
How the Test Runner uses these
When the FixturFab Test Runner launches a plan it sets --backend_url, --run_id, --plan_id, --slot_id, and --frontend_client_id so results stream back to the correct run and slot. See With the Test Runner. Running locally you can ignore all of them except --f3ts_config — and only if your config file isn't named config.yml.