-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
HTTP / TCP Test Harness for JSON RPC #52
Draft
praetoriansentry
wants to merge
9
commits into
main
Choose a base branch
from
jhilliard/DVT-581-test-harness-for-reliability-tests
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
HTTP / TCP Test Harness for JSON RPC #52
praetoriansentry
wants to merge
9
commits into
main
from
jhilliard/DVT-581-test-harness-for-reliability-tests
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
LKS121
reviewed
Jun 26, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done
LKS121
reviewed
Jun 26, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Review
This was referenced Jun 26, 2024
Closed
Comment on lines
+107
to
+117
//A server that's listening on UDP rather tha TCP | ||
//A server that responds with valid data but with a delay (e.g. a 2-second delay) | ||
//A server that returns data with invalid or malformed JSON syntax | ||
//A server that returns data in a different character encoding than expected (e.g. ISO-8859-1 instead of UTF-8) | ||
//A server that responds with a different HTTP status code than expected (e.g. 301 instead of 200) | ||
//A server that sends back a response that exceeds the content-length specified in the response header | ||
//A server that sends back a response with missing headers | ||
//A server that sends back a response with extra headers | ||
//A server that requires an authentication header, but fails if it is not provided or if it is incorrect | ||
//A server that requires a specific content type header, and fails if it is not provided or if it is incorrect | ||
//A server that has a firewall that blocks certain IP addresses, causing the request to fail. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Suggested change
//A server that's listening on UDP rather tha TCP | |
//A server that responds with valid data but with a delay (e.g. a 2-second delay) | |
//A server that returns data with invalid or malformed JSON syntax | |
//A server that returns data in a different character encoding than expected (e.g. ISO-8859-1 instead of UTF-8) | |
//A server that responds with a different HTTP status code than expected (e.g. 301 instead of 200) | |
//A server that sends back a response that exceeds the content-length specified in the response header | |
//A server that sends back a response with missing headers | |
//A server that sends back a response with extra headers | |
//A server that requires an authentication header, but fails if it is not provided or if it is incorrect | |
//A server that requires a specific content type header, and fails if it is not provided or if it is incorrect | |
//A server that has a firewall that blocks certain IP addresses, causing the request to fail. | |
//A server that's listening on UDP rather than TCP. | |
//A server that responds with valid data but with a delay (e.g. a 2-second delay). | |
//A server that returns data with invalid or malformed JSON syntax. | |
//A server that returns data in a different character encoding than expected (e.g. ISO-8859-1 instead of UTF-8). | |
//A server that responds with a different HTTP status code than expected (e.g. 301 instead of 200). | |
//A server that sends back a response that exceeds the content-length specified in the response header. | |
//A server that sends back a response with missing headers. | |
//A server that sends back a response with extra headers. | |
//A server that requires an authentication header, but fails if it is not provided or if it is incorrect. | |
//A server that requires a specific content type header, and fails if it is not provided or if it is incorrect. | |
//A server that has a firewall that blocks certain IP addresses, causing the request to fail. |
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.
Description
Creating a basic test harness based on the idea from Release It / Michae Nygard. The goal is to use this while testing our JSON proxies and various blockchain components. Eventually we may want to drop down to an even lower level to handle stuff like sending
RST
packets or fiddling with the controls of TCP.Jira / Linear Tickets