feat(loadtesting): ship the Load Testing capability index on main - #458
Open
sourabhd-cbu wants to merge 1 commit into
Open
sourabhd-cbu wants to merge 1 commit into
sourabhd-cbu wants to merge 1 commit into
Conversation
Brings the loadtesting capability index from feat/capability-registry (where it has been developed and reviewed: #449, #450, #451) onto main so it ships in the published package — main already carries the registry loader that discovers it, but no loadtesting index, so releases cut from main (e.g. v2.1.0) expose no Load Testing capabilities. - capability/loadtesting.capability-index.json — 21 capabilities, typed <Cap>Data response schemas, same-test compareLoadTestRuns contract, 'API' testType labels, duration-in-minutes report guidance - tests/tools/loadtestingCapabilityIndex.test.ts - scripts/contract-baseline/loadtesting.json (0 / 0) and a loadtesting step in npm run check:contract, so the 0-unbacked state is enforced Only loadtesting files; the rest of feat/capability-registry is not included. Full suite 1127/1127; check:contract OK for tm and loadtesting.
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the ⚙️ Run configuration
You can disable this status message by setting the Use the checkbox below for a quick retry:
Comment |
sarve-shreyas
approved these changes
Oct 5, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
The Load Testing capability index has only ever lived on
feat/capability-registry(developed and reviewed there: #449, #450, #451).mainalready carries the registry loader that discovers per-product indexes — and its code already anticipates a loadtesting index — but has nocapability/loadtesting.capability-index.json. So releases cut frommain(e.g. v2.1.0) expose no Load Testing capabilities; they only reach users through manual beta builds of the feature branch.What
Only the loadtesting files, taken as-is from
feat/capability-registry:capability/loadtesting.capability-index.json— 21 capabilities with typed<Cap>Dataresponse schemas, the same-testcompareLoadTestRunscontract (matches load-testing-backend#3135, merged), 'API' testType labels, duration-in-minutes report guidancetests/tools/loadtestingCapabilityIndex.test.tsscripts/contract-baseline/loadtesting.json(0 capabilities / 0 unbacked fields)package.json: a loadtesting step innpm run check:contract, so the 0-unbacked state is enforced on mainNo other
feat/capability-registrychanges (live tests, loader changes, tm edits) are included — main's registry code is newer than the feature branch's.Testing
npm run check:contract: tm 16/60 vs baseline 16/60 OK; loadtesting 0/0 vs baseline 0/0 OKImpact
Merging means the next published release exposes the Load Testing tools to all users, not only beta builds.