Integration tests get lambda output #242
Merged
Conversation
This file contains 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
laurenfrederick
approved these changes
Mar 13, 2018
|
@laurenfrederick I think I will wait until we make a release and then update all the tests (including adding the test that I needed this change for) |
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.
Summary: @cumulus/integration-tests lambda.js#getLambdaOutput returns entire lambda output, not just he payload.
Test Plan
./bin/cli.js workflow --stack-name aimee-deploy-cumulus --bucket-name cumulus-devseed-internal --workflow HelloWorldWorkflow --input-file ./helloWorldInput.json. This doesn't test this function but it does test it didn't break anything else.I think it is useful to test the full cumulus message in integration tests - I will be using this in cumulus-integration-tests