Repository navigation
test(pipeline): expect SUPERSEDED execution mode - #8
Merged
Merged
Conversation
The deployment-pipeline test pinned ExecutionMode to QUEUED and broke after switching the pipeline to SUPERSEDED, failing the CodeBuild Verify stage (and the GitHub lint-and-test check). Update the assertion and test title to match the intended SUPERSEDED behaviour.
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
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.
Follow-up to the SUPERSEDED pipeline change.
src/tests/deployment-pipeline.test.tsstill assertedExecutionMode === 'QUEUED', which broke the CodeBuild Verify stage and the GitHublint-and-testcheck once the stack moved to SUPERSEDED. Updates the assertion and test title.Local verification:
npm run lintpass;npm test498/498 pass.