-
Notifications
You must be signed in to change notification settings - Fork 29
Initial whole-stack tests for the API Server #1259
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
Conversation
This generally looks OK, besides the comments I made. It's still in draft, so I'm not sure what's left. |
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.
Just a quick first pass
If you look at |
Given the tests file is already over 1000 lines, would it make sense to break it down by endpoint tested? I guess the categorisation is not going to be 100% accurate since I can imagine tests that check a combination of endpoints but maybe better than a monolithic file. |
e662369
to
3fd89cb
Compare
I use code folding in Emac a lot, and because I've put each set of tests within a separately named module within the file, when the test file is collapsed, it logically makes sense. Not as clear as spreading this out to multiple files though, but code folding does let you see the shape of the file and lets you drill down when needed. |
I've added a few transaction() and transaction_merkle_path() tests, but there a many TODOs left in the comments. This PR is getting quite big as it is, so maybe the TODOs can be done in a separate PR along with the Destination and Pool endpoint changes / tests. |
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.
Besides the TODOs, this is looking fine. I'm assuming these TODOs will be fixed next.
57b4967
to
9a5ef7a
Compare
Part of #1189