[TIP] - ATP problem

yoav glazner yoavglazner at gmail.com
Wed Aug 26 21:23:30 PDT 2009

I have tried to play with the auto-doc ext and it seems to be half
automatic, isn't there a way to automatically take unit test and make a
docuent/html that explains the tests?

On Wed, Aug 19, 2009 at 4:05 PM, Jesse Noller <jnoller at gmail.com> wrote:

> For test specifications; I've tended to use Sphinx (sphinx.pocoo.org)
> and the autodoc extension. I tend to document my tests and modules
> pretty heavily, and so doing this allows me to extract nice-looking
> and easy to use documentation from my tests, and accentuate as needed.
> The nice thing with doing it this way, is that you can add further
> examples/notes/etc on top of what is within the test code itself. It
> also helps keep you disciplined about documentation on the tests and
> any supporting modules. All of the docs are in Restructured Text,
> which is close to the perfect markup :)
> On Wed, Aug 19, 2009 at 7:07 AM, yoav glazner<yoavglazner at gmail.com>
> wrote:
> > Hi all,
> > I have a problem in my work, they want me to an "ATP".
> > which means a long Word document that expalains what tests are made.
> > no one will ever really read this document.
> > i was thinking on making the acceptance tests on top of
> unittest/pymock/nose
> > and generate someting like the ATP,
> > from the testFunctions docs.
> > is something like this already available?
> > Thanks a lot,
> > Yoav Glazner
> > _______________________________________________
> > testing-in-python mailing list
> > testing-in-python at lists.idyll.org
> > http://lists.idyll.org/listinfo/testing-in-python
> >
> >
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.idyll.org/pipermail/testing-in-python/attachments/20090827/0c91f144/attachment.htm 

More information about the testing-in-python mailing list