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
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
This PR adds scenario tier categorization to TypeSpec HTTP specs to enable better test coverage management and dashboard filtering.
Changes:
Dashboard Enhancement:
Added tier-based filtering dropdown to the spec coverage dashboard
Scenarios can now be filtered by "core" or "extended" tiers
UI shows tier selection status and filtered scenario counts
Spec Categorization:
Added @scenarioTier decorator to 56 TypeSpec spec files across all HTTP spec categories
Core tier (essential scenarios): Authentication, basic Parameters, Routes, Server, Type operations, Versioning, etc.
Extended tier (advanced scenarios): Complex routing expansions, XML payloads, discriminated unions, streaming, etc.
Applied decorators strategically at namespace, interface, or operation level based on scenario groupings
Impact:
Enables focused testing and development by allowing teams to run core scenarios first, then extended ones
Improves dashboard usability for large test suites
Maintains backward compatibility - no breaking changes to existing specs
The tier classification follows the pattern: core scenarios cover fundamental HTTP/REST functionality while extended scenarios test advanced features and edge cases.
Add scenario tier support to categorize scenarios as "core" or "extended",> ,> - Add @scenarioTier decorator to TypeSpec HTTP specs for better test organization,> - Update spec dashboard to support tier-based filtering of scenarios,> - Enable teams to focus on core functionality testing before extended features
Add scenario tier support to categorize scenarios as "core" or "extended",> ,> - Add @scenarioTier decorator to TypeSpec HTTP specs for better test organization,> - Update spec dashboard to support tier-based filtering of scenarios,> - Enable teams to focus on core functionality testing before extended features
Add scenario tier support to categorize scenarios as "core" or "extended",> ,> - Add @scenarioTier decorator to TypeSpec HTTP specs for better test organization,> - Update spec dashboard to support tier-based filtering of scenarios,> - Enable teams to focus on core functionality testing before extended features
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.
joheredi
force-pushed
the
joheredi/spector-tiers
branch
from
This PR adds scenario tier categorization to TypeSpec HTTP specs to enable better test coverage management and dashboard filtering.
Changes:
Dashboard Enhancement:
Spec Categorization:
@scenarioTierdecorator to 56 TypeSpec spec files across all HTTP spec categoriesImpact:
The tier classification follows the pattern: core scenarios cover fundamental HTTP/REST functionality while extended scenarios test advanced features and edge cases.