Go to the latest version of this document.
search in docstrings

Search bar offers the following options:

- Term presence. The below example searches for documents that must contain “foo”, might contain “bar” and must not contain “baz”: `+foo bar -baz`
- Wildcards. The below example searches for documents with words beginning with “foo”: `foo*`
- Search in specific fields. The following search matches all objects in "twisted.mail" that matches “search”: `+qname:twisted.mail.* +search`

  Possible fields: 'name', 'qname' (fully qualified name), 'docstring', and 'kind'. Last two fields are only applicable if "search in docstrings" is enabled.

- Fuzzy matches. The following search matches all documents that have a word within 1 edit distance of “foo”: `foo~1`

Results provided by Lunr.js

# ``twisted`.`trial`.`_asyncrunner``

module documentation
(source)

Infrastructure for test running and suites.

Class | `_BrokenIDTestCaseAdapter` | Adapter for pyunit-style `TestCase` subclasses that have undesirable id() methods. That is `unittest.FunctionTestCase` and `unittest.DocTestCase`.
Class | `_ForceGarbageCollectionDecorator` | Forces garbage collection to be run before and after the test. Any errors logged during the post-test collection are added to the test result as errors.
Class | `_PyUnitTestCaseAdapter` | Adapt from pyunit.TestCase to ITestCase.
Function | `_clearSuite` | Clear all tests from `suite`.
Function | `_iterateTests` | Iterate through all of the test cases in `testSuiteOrCase`.
Variable | `_docTestCase` | Undocumented

def _clearSuite(suite): (source)

Clear all tests from `suite`.

This messes with the internals of `suite`. In particular, it assumes that the suite keeps all of its tests in a list in an instance variable called `_tests`.

def _iterateTests(testSuiteOrCase): (source)

Iterate through all of the test cases in `testSuiteOrCase`.

_docTestCase = (source)

Undocumented