Skip to content

feat(loadtesting): add runId to updateLoadTest for run-level tagging - #402

Merged
sourabhd-cbu merged 1 commit into
browserstack:feat/capability-registryfrom
sourabhd-cbu:feat/loadtesting-run-tags
Sep 8, 2026
Merged

feat(loadtesting): add runId to updateLoadTest for run-level tagging#402
sourabhd-cbu merged 1 commit into
browserstack:feat/capability-registryfrom
sourabhd-cbu:feat/loadtesting-run-tags

Conversation

@sourabhd-cbu

Copy link
Copy Markdown
Collaborator

Index-only. Exposes an optional runId on the updateLoadTest capability so the agent can tag a specific run instead of the test definition.

Why it's needed

The backend (load-testing-backend PR #2845) now accepts runId on updateLoadTest — when set, config.tags is applied to that run's own tags (job.meta.labels) and the test is untouched. But the generic invokeEndpoint strictly rejects any body field not declared in the capability (bind.ts: "unknown arguments are an error"), so without declaring runId here the MCP would throw unknown body: runId before the request reached the backend. This index change is what lets the MCP pass runId through.

Change

  • updateLoadTest body gains optional runId (string): "Tag a specific RUN instead of the test definition; only config.tags may accompany it; omit to edit the test."
  • Guidance: run-vs-test tag semantics, override-and-inherit (a run inherits the test's tags until set; setting overrides and replaces wholesale — send the union to add).

Follow-up to the merged #400. Backend counterpart: browserstack/load-testing-backend #2845.

Backend now supports tagging a specific run via updateLoadTest with a `runId`
(config.tags applied to the run, test definition untouched). Expose the optional
`runId` body field + guidance: run vs test tag semantics, override-and-inherit,
and that only config.tags may accompany runId.
@coderabbitai

coderabbitai Bot commented Sep 8, 2026

Copy link
Copy Markdown

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Central YAML (base), Organization UI (inherited), Workspace UI (inherited)

Review profile: ASSERTIVE

Plan: Enterprise

Run ID: a0e40698-3e91-4835-96e5-212a35371090

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

Comment @coderabbitai help to get the list of available commands.

@sourabhd-cbu
sourabhd-cbu merged commit 5732f78 into browserstack:feat/capability-registry Sep 8, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant