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
just a small refactor of api_test #291
Conversation
85c0a20
to
492ceb5
Compare
This makes the test more hermetic by avoiding the need to set env vars, and it also avoids some unecessary duplication of test helper logic by leveraging some of aetest's underlying implementation. This change was originally part of golang#284, but I split it out because it's not compatible with v1's log flushing tests, and it would have added unecessary noise to that PR.
492ceb5
to
6fa552f
Compare
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.
Thanks!
Can you resolve the conflicts we see now? |
oh, whoops. i didn't realize this was approved but unmerged. |
huh, i resolved the conflicts in the github UI, but now the tests are failing because python2 is missing, so I don't have full confidence that I didn't mess something up in the merge... |
I've a PR in review. Once in, I will merge yours to be sure. |
This makes the test more hermetic by avoiding the need to set env vars, and it also avoids some unecessary duplication of test helper logic by leveraging some of aetest's underlying implementation (namely RegisterTestRequest).
This change was originally part of #284, but I split it out because it's not compatible with v1's log flushing tests, and it would have added unecessary noise to that PR.