Support for direct calls to execute lambda functions and return their output (for py.tests) #35
Conversation
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
The return value of the functions is returned so the test can check the output.
yxd-hde
approved these changes
Oct 12, 2018
freedomofkeima
approved these changes
Oct 23, 2018
|
Related PR: #41 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
When writing py.tests for lambda functions that have a non-empty return, each test function should create a test event/context, execute the lambda with the event/context and then compare the output of the function with the expected output.
This is currently not possible with the package as the command-line is its only interface.
This PR adds the feature for py.test functions (or any other module for that matter) to execute the lambda locally, and get the output.