This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author xtreak
Recipients Petter S, THRlWiTi, asvetlov, dave-shawley, miss-islington, njs, pdxjohnny, r.david.murray, xtreak, yselivanov, zach.ware
Date 2019-09-10.15:55:41
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1568130942.11.0.595542325563.issue32972@roundup.psfhosted.org>
In-reply-to
Content
I did an initial try at the documentation. I think most of the functions are very similar to the TestCase API and I just copied them to add the async related information. I guess it could be improved to keep the length down with still retaining the link to synchronous API. I added an example of a coroutine test case with the order of setup and teardown calls. 

I also realized during the docs that there is no async versions of class level setup and teardown calls. They are executed in a slightly different manner in unittest.suite module unlike per test setup and teardown. Is this an explicit decision to not support them? Is it worth documenting them?

Feedback welcome.
History
Date User Action Args
2019-09-10 15:55:42xtreaksetrecipients: + xtreak, r.david.murray, njs, asvetlov, THRlWiTi, zach.ware, yselivanov, miss-islington, pdxjohnny, Petter S, dave-shawley
2019-09-10 15:55:42xtreaksetmessageid: <1568130942.11.0.595542325563.issue32972@roundup.psfhosted.org>
2019-09-10 15:55:42xtreaklinkissue32972 messages
2019-09-10 15:55:41xtreakcreate