Add regression tests for numeric version type handling #8247
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.
After fixing three version field type handling issues, add comprehensive regression tests to prevent future inconsistencies when handling string, int, and float version types.
Changes
Created
pkg/workflow/engine_test.gowith version type tests covering:Verified existing coverage in
pkg/parser/mcp_test.go:Test Coverage
All three version fields now have regression protection:
Similar coverage exists for
tools.github.versionandtools.playwright.versionin existing MCP tests.Original prompt
💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.