Re: probably stupid question about automated testing and reactor.run
Chris Norman <[email protected]>
| Newsgroups | gmane.comp.python.twisted |
|---|---|
| Message-ID | <CANjhqb-g6-039OqoOVxYqqLPEN5iXKSsUXoLwseFYtuyKG0spA@mail.gmail.com> |
Hi, First of all please take what I'm about to say with a pinch of salt, as I really don't know what I'm talking about half the time. As reactors can only be started once, I would imagine calling it from a test function would be largely pointless. Depending on what test suite you're using there should be a way of calling reactor.stop() at the end though... or something. HTH, On Wed, 7 Nov 2018 at 16:14, Chris Withers <[email protected]> wrote: > Hi All, > > Sorry, the silly questions about testing keep coming... > > Is it legit for a unit testable piece of an application's code to call > reactor.run()? > > How do you feed a reactor.stop() into such a test? Would that be a sane > thing to try and do? > > How do people deal with this kind of testing? > > cheers, > > Chris > > _______________________________________________ > Twisted-Python mailing list > [email protected] > https://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python > -- Take care, Chris Norman _______________________________________________ Twisted-Python mailing list [email protected] https://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python