Skip to main content

Service Parameters

:::info Screenshot needed — light/dark 📸 settings-window-light.png and settings-window-dark.png — Settings Window, custom title bar :::

The Service Parameters tab provides per-service configuration. Each service instance registered in your project exposes its own set of adjustable parameters, organized in expandable sections. The list and descriptions are generated dynamically from the service classes (FrameworkSettings.ServiceParameters), so the exact parameters shown depend on which service types are present in your workspace.

Service Parameters tab with an expander per service type showing its parameters

How It Works​

  1. Each supported service type appears as an expander whose header is the friendly name of the service instance (resolved from the service class via ServiceInstanceToNameConverter).
  2. Expanding a service shows its description (resolved from the service class via ClassToDescriptionConverter) followed by its editable parameters.
  3. Each parameter is rendered by a type-appropriate editor (ParameterControl) — textboxes, toggles, dropdowns, or numeric fields — depending on the parameter's underlying type.
  4. Changes are saved together with the rest of your settings when you auto-save on close.
note

Service parameters act as defaults. Individual requests, test steps, and environment variables can override them with more specific values.

Common Parameter Categories​

Parameters vary by service type, but most service definitions group them into a few recurring categories. Typical examples include:

CategoryExample Parameters
ConnectionTimeout (ms), retry count, keep-alive
EndpointsDefault base URL, fallback URLs
AuthenticationDefault auth type, credential references
LimitsMax response size, rate limiting
TLSCertificate validation, client certificates

Each parameter label and description comes directly from the service's definition, so refer to the in-UI description under each field for the authoritative meaning.

Use Cases​

  • Increase timeouts for slow-responding services without changing individual test step settings.
  • Set default authentication so every new request to a service uses the same credentials.
  • Override endpoints for testing against staging or local instances globally.

See Also​

Last updated on