Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #7223

Closed
Open
Created Oct 26, 2012 by Arturo Filasto@art

Streamline the creation of test specifications

Currently we write test specifications here: https://trac.torproject.org/projects/tor/wiki/doc/OONI/Tests, but we also include the details of a test inside of the code.

To avoid having to manually keep in sync the test specification on the wiki and the one inside of the code it would be ideal if we had a way to automatically generate from the code the test specification.

We should take the data from the docstrings of the test specification and create markup to go on either the trac wiki page or on the OONI docs stored on https://ooni.readthedocs.org/

I see to possible routes for doing this:

  1. we do something custom that runs on every file the methods that we use in runner.py do detect if a class if of the right class and then using something similar to this: https://github.com/globaleaks/GLBackend/blob/master/docs/generate_spec.py we generate the test specification

  2. Use the autodoc feature of sphinx: http://sphinx.pocoo.org/ext/autodoc.html#module-sphinx.ext.autodoc.

I believe the second option is optimal.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking