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

TestTorch.test_doc should be in TestDocCoverage #28033

Open
zou3519 opened this issue Oct 15, 2019 · 6 comments
Open

TestTorch.test_doc should be in TestDocCoverage #28033

zou3519 opened this issue Oct 15, 2019 · 6 comments
Labels
module: doc infra Related to pytorch.org/docs, deployment of, and serving module: docs Related to our documentation, both in docs/ and docblocks triaged This issue has been looked at a team member, and triaged and prioritized into an appropriate module

Comments

@zou3519
Copy link
Contributor

zou3519 commented Oct 15, 2019

Afaict TestTorch.test_doc tests that certain functions on torch are documented. This is similar to what TestDocCoverage does and it would be great to have all of the documentation tests in one single location.

def test_doc(self):

cc @ezyang @zou3519

@smessmer smessmer added module: doc infra Related to pytorch.org/docs, deployment of, and serving module: docs Related to our documentation, both in docs/ and docblocks triaged This issue has been looked at a team member, and triaged and prioritized into an appropriate module labels Oct 17, 2019
@ayush-1506
Copy link

@zou3519 I'd like to work on this issue, if that's not a problem? Please let me know if I should go ahead.

@ezyang
Copy link
Contributor

ezyang commented Oct 20, 2019

Sure! However, I am not sure we are quite clear what exactly should be done here (unless @zou3519 you have a better idea than me). I suggest reading the code and then writing up a short proposal here that we can check over before you start coding.

@ayush-1506
Copy link

From what I could understand, the overall objective is to move the test_doc to a member function inside TestDocCoverage (here), since testing for documented functions is the purpose of both these.

At the moment I don't see any caveats, but given that I've merely skimmed over the code, I'd be grateful if someone could verify my understanding and let me know if I've missed something.

cc @ezyang @zou3519

@ayush-1506
Copy link

Ping @ezyang @zou3519

@zou3519
Copy link
Contributor Author

zou3519 commented Oct 25, 2019

When I opened this issue, I was thinking that we should consolidate all of our docs tests into one test file. i.e., TestTorch.test_doc and TestTorch.test_doc_template should be moved into the same test file as TestDocsCoverage.

The reason for this is to consolidate our docs tests and to perhaps share a blacklist/whitelist between them. Perhaps we should move TestTorch.test_doc and TestTorch.test_doc_template into a new TestCase that is named something like "TestDocstrings" and toss it into test_docs_coverage.py?

@ayush-1506
Copy link

Right, that probably makes sense. Please let me know if I should go ahead with this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
module: doc infra Related to pytorch.org/docs, deployment of, and serving module: docs Related to our documentation, both in docs/ and docblocks triaged This issue has been looked at a team member, and triaged and prioritized into an appropriate module
Projects
None yet
Development

No branches or pull requests

4 participants