Setup ecu.test agent¶

Open Options ‣ Settings ‣ ecu.test agent to connect the workspace to the Agent service and configure button-based generation and multimedia processing.

Connection¶

URL

Base URL of the Agent service. This must be a valid URL, secured via HTTPS.

API key

Key used to authenticate with the Agent service. Use the button next to the input field to show or hide the key.

Connection status

Select Check to verify the connection. A successful connection is shown as OK. When the connected service provides credit information, the remaining credits are shown as well.

Generation model

Model used exclusively for Button-based generation, including test step and trace step generation. Chat has a separate model selection, as described in Configure your chat.

Select a model from the list or enter its name. Use the refresh button next to the field to retrieve the available models from the configured service.

Proxy settings

Optional proxy configuration. The supported modes are: no proxy, system proxy, and a user-defined proxy with optional authentication. Browser and PAC proxies are not supported.

Advanced

Allow insecure connection (not recommended) disables verification of the secure service connection.

Reference implementation contexts¶

Reference implementations allow button-based test step generation to use patterns from existing Packages. Each named context points to a directory containing representative Packages.

To add a context:

1. Select the tab with the plus icon.

2. Enter a unique name.

3. Set the path to the directory containing the Packages. Workspace-relative paths are supported.

4. Keep Enable selected if the context should be available to generation.

Right-click a context tab to rename it. Close the active tab to remove that context.

The active contexts can also be selected from the button-based generation dropdown. See Using reference implementations for how references are selected and updated.

Filter settings¶

Filter settings limit how many items of each category can be included in one button-based test step generation request. ecu.test agent selects the most relevant items for the current Block description from the available workspace content.

Signal mappings

Maximum number of signal mappings.

Jobs

Maximum number of Tool and Port Jobs.

Package mappings

Maximum number of mapped Packages.

Packages from library workspaces

Maximum number of Packages from configured library workspaces.

Package variables

Maximum number of variables from the current Package.

Global constants

Maximum number of constants from the current configuration.

Reference implementation blocks

Maximum number of similar Blocks from enabled reference implementation contexts.

The sum of all filter limits must not exceed 50. Higher limits provide more context, but can increase request size and generation time without necessarily improving the result.

Custom instructions¶

Custom instructions provide project-specific guidance for button-based generation. Separate tabs are available for test cases and trace analyses. Each field accepts up to 3000 characters.

Use clear, specific instructions, for example:

• naming conventions for variables and parameters

• preferred units and time options

• mappings that may or may not be written

• required test step patterns

• domain-specific rules

See Improving generated test steps for further guidance. Chat does not use these fields for its Package review rules. The Chat review subagent uses package_rules.md instead, as described in Review Agent.