Currently Testimony leverages the AST Python module in order to capture the docstrings in order to parse them to generate its reports.
Would be great if Testimony actually import the modules and let dynamic things, like Python decorators, to run. This is the same thing Sphinx does to generate documentation and we can leverage it as a library or get some ideas on how to do.
A use case I can think of is test skipping decorators based on open bugs, the decorators can append the @bz tag automatically to the test docstring, making it much easier to maintain the code since the writer will not be required to add it manually.
sthirugn
commented
8 years ago
Currently Testimony leverages the AST Python module in order to capture the docstrings in order to parse them to generate its reports.
Would be great if Testimony actually import the modules and let dynamic things, like Python decorators, to run. This is the same thing Sphinx does to generate documentation and we can leverage it as a library or get some ideas on how to do.
A use case I can think of is test skipping decorators based on open bugs, the decorators can append the
@bztag automatically to the test docstring, making it much easier to maintain the code since the writer will not be required to add it manually.