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
Drop testtools
support?
#2156
Labels
Milestone
Comments
Another option is to drop |
I have no opinion on this, either way works for me |
I don't think we need to keep supporting it. It's a minor convenience left over from early OpenStack days for a very small community relative to the broader python ecosystem. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
At the time of writing, our documentation might give an impression that using
testtools
is the preferred way to write tests for a Falcon app.I haven't done any research or survey in the area, but just subjectively it feels that the most popular testing frameworks in 2023 are
pytest
followed by the stdlib'sunittest
(both are also well supported by Falcon).Moreover, IIRC I had to exclude
testtools
from our test dependencies when adding Python 3.10 CI gates, since it wasn't 3.10-ready by the time. So it's becoming a maintenance burden, too.OTOH, it seems that there has been a new
testtools
release, and the project is still maintained. So after all maybe it doesn't hurt to keep the integration?Even if we decide to keep
testtools
, we should IMHO reword the docs not to give the impression it is the preferred way, and link to our tutorial for usingpytest
in the same paragraph.The text was updated successfully, but these errors were encountered: