chore: Add snapshot test for Go stacks #313
Merged
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.
What does this PR do?
Add a Go stack to snapshot tests, so that the test will compare the snapshots generated after vs before, to check if a PR causes unexpected changes on the stack to be deployed.
The stack was copied from
examples/go-stack
. I had to copy it because I don't think it's possible to just reference the existing stack.Motivation
Adding more tests to make it safer to deploy changes.
Testing Guidelines
To ensure the example stack uses the locally built Go package instead of the production package, I:
applyEnvVariables()
inenv.ts
:so an extra environment variable will be added to the Lambda function.
yarn build
aws-vault exec sso-serverless-sandbox-account-admin -- scripts/run_integration_tests.sh
Result:
The test failed. The generated snapshot has the new environment variable, which captures the unintended change.
Additional Notes
Types of Changes
Check all that apply