RFC Testing Scenario #282
Open
RFC Testing Scenario #282
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
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.
This is a request for comment (RFC) about how we can improve testing for Twilio Functions. This is a proposal and all opinions are welcome. The design serves as an example and foundation for discussion.
How to interact with this RFC:
Head into the "Files Changed" tab and on the file click "Display Rich Diff" on the right side or read the RFC in markdown. For questions or suggestions that are directly related to the content of the RFC, add single line comments in the respective places. Only perform a full review if you feel strongly about something having to change.
For things that are not directly mentioned in the RFC, for example because you believe they are missing, you can comment directly in this Pull Request thread.
Contributing to Twilio