On 21/02/2022 12:45, Adi Roiban wrote:
On Sun, 20 Feb 2022 at 22:48, Kyle Altendorf <[email protected]> wrote:
On Sun, Feb 20, 2022, at 13:44, Chris Withers wrote:
At this point, it feels like any available energy could be more usefully
employed in getting a pytest plugin that really supported the Twisted
reactor in place. Re-inventing wheels like coverage just doesn't seem
sensible at this point.
I don't expect to invest a lot of time in pytes-twisted, but I am curious what
you mean by supporting the Twisted reactor in place. A new reactor for each
test?
FYIW I'm also +1 to try to get Twisted support for pytest , stdlib
unit test or nose.
I think nose is pretty much dead and note sure I know anyone using the
stdlib discovery stuff...
I guess that many of the existing Twisted based projects are using
`trial` so things are not that easy.
If you're doing a twisted project, I think you kinda have to be using
trial. I wrote carly to cover the "real networking in tests" pattern, no
docs, but its test suite shows you what it does, eg:
https://github.com/cjw296/carly/blob/master/tests/test_web_site.py
For now, for my project I am running Twisted tests with trial and some
custom realtor start and stop, but the long term plan is to migrate to
pytest.
Interested to hear more about custom reactor start and stop...
Chris
_______________________________________________
Twisted mailing list -- [email protected]
To unsubscribe send an email to [email protected]
https://mail.python.org/mailman3/lists/twisted.python.org/
Message archived at
https://mail.python.org/archives/list/[email protected]/message/VOO5K2ZFVDJUPTG4F4VKEEPYBL5JEHWL/
Code of Conduct: https://twisted.org/conduct
