You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
test: Split the default-listing case into explicit telemetry on/off cases, mark critical
The old single case asserted telemetry off (report-problem absent) via the
suite's own default, never setting telemetry explicitly. internal's own
tool-loading.cases.ts carried a near-duplicate asserting the opposite
(report-problem present, since its hosted deploy runs telemetry on by
default) - same scenario, diverging only because of which suite's default
happened to apply, not a real behavioral difference worth two separate
hand-maintained tests in two repos.
Now: two cases, each forcing telemetry via withClient's own option instead
of relying on any suite/environment default, both critical so internal gets
both automatically. Each asserts the full tools list, not just
report-problem's presence - confirms toggling telemetry changes only that
one tool, nothing else shifts.
Also adds 'should handle mixed categories and specific tools in tools param'
(moved from internal's tool-loading.cases.ts as-is, marked critical) - pure
tools_loader selector-merging logic with no hosting dependency and no
existing similar case here.
0 commit comments