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

Refactor greentest and test code #1293

Closed
jamadden opened this Issue Oct 18, 2018 · 1 comment

Comments

Projects
None yet
1 participant
@jamadden
Member

jamadden commented Oct 18, 2018

If we want to encourage extensions and plugins to gevent (ala #1158), then it's likely authors of such plugins would benefit from gevent's tustrunner, test class bases, assertion methods, platform support and stdlib monkey-patch tests.

Ideas:

  • src/greentest/greentest should move to src/gevent/testing/
  • src/greentest/test_* should move to src/gevent/tests/
  • src/greentest/py* (the stdlib tests) can stay where they are, for reduced install sizes, or they can be distributed in src/gevent/tests/ or src/gevent/testing/ so that downstream authors can run the monkey-patched tests

@jamadden jamadden added the in progress label Nov 7, 2018

@jamadden

This comment has been minimized.

Member

jamadden commented Nov 7, 2018

We'll want some minimal documentation, clarifying that gevent.testing is available for use, but the API is subject to change.

jamadden added a commit that referenced this issue Nov 7, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment