Add WCI valid/invalid compute configs tests#69
Merged
Conversation
This adds a test for duplicate worker deployment versions and then various test around creating and updating worker deployment versions with valid and invalid compute configs.
|
|
02strich
approved these changes
Jul 2, 2026
jaypipes
approved these changes
Jul 2, 2026
jaypipes
left a comment
jaypipes
left a comment
Contributor
There was a problem hiding this comment.
Yup, nicely written tests, thanks @justinschoeff :)
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
6 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.
This adds a test for duplicate worker deployment versions and then
various test around creating and updating worker deployment versions
with valid and invalid compute configs.
What was changed
New integ test cases covering worker deployment version requests specifically around compute config which triggers WCI workflow.
Why?
Reach desired automated coverage for serverless release.
Checklist
Closes n/a
How was this tested:
Is test
No