Skip to content
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

Make use of testHeader and testMethod consistent #829

Closed
sahildua2305 opened this issue Jan 12, 2018 · 1 comment
Closed

Make use of testHeader and testMethod consistent #829

sahildua2305 opened this issue Jan 12, 2018 · 1 comment
Assignees

Comments

@sahildua2305
Copy link
Member

sahildua2305 commented Jan 12, 2018

As found out while reviewing #817, we have some inconsistencies in our tests where some of the tests don't use the testHeader and testMethod functions to test request header and method.

One of the defaulter is https://github.com/google/go-github/blob/master/github/git_trees_test.go#L22.

This is completely harmless. Though it's important to make sure it doesn't cause further confusion for the new contributors as it did in that PR initially.

Via this issue, I'd like to point it out and mention that I'd like to fix this inconsistency.

@willnorris
Copy link
Collaborator

sounds good to me. assigned to you.

sahildua2305 added a commit to sahildua2305/go-github that referenced this issue Jan 14, 2018
Use testMethod to test the request method instead of manually comparing
it and testing. This change is to make things consistent through out the
code base.

Fixes google#829
gmlewis pushed a commit that referenced this issue Jan 16, 2018
Use testMethod to test the request method instead of manually comparing
it and testing. This change is to make things consistent through out the
code base.

Fixes #829.
nbareil pushed a commit to nbareil/go-github that referenced this issue May 1, 2018
Use testMethod to test the request method instead of manually comparing
it and testing. This change is to make things consistent through out the
code base.

Fixes google#829.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants