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.

Sign up for GitHub

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

Jump to bottom

How should we exercise snippets via testing? #1744

Closed
tseaver opened this issue Apr 22, 2016 · 1 comment
Closed

How should we exercise snippets via testing? #1744

tseaver opened this issue Apr 22, 2016 · 1 comment
Assignees
@tseaver
Labels
testing type: question Request for information or clarification. Not an issue.

Comments

@tseaver
Copy link
Contributor

tseaver commented Apr 22, 2016

The snippets introduced in #1690 are intended to be testable against the API (almost system tests). @dhermes brought up the following issues about them:

[We need]

A clear story on when these snippets are run (i.e. update tox.ini)
Way fewer pylint disable statements
Integrating with unittest, it seems your main() is emulating some of that functionality.
@tseaver tseaver added type: question Request for information or clarification. Not an issue. testing api: pubsub Issues related to the Pub/Sub API. labels Apr 22, 2016
@tseaver tseaver mentioned this issue Apr 22, 2016
Merged
@dhermes dhermes mentioned this issue Aug 22, 2016
Closed
@theacodes theacodes mentioned this issue Aug 22, 2016
Closed
@tseaver tseaver removed the api: pubsub Issues related to the Pub/Sub API. label Aug 25, 2016
@tseaver
Copy link
Contributor Author

tseaver commented Aug 25, 2016

#2154 supersedes this for the general case.

@tseaver tseaver closed this as completed Aug 25, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@tseaver tseaver

Labels
testing type: question Request for information or clarification. Not an issue.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@tseaver