Opened 11 years ago

Closed 8 years ago

Last modified 7 years ago

#7474 closed (wontfix)

add documentation restructured text checker to test suite

Reported by: Gary Wilson Owned by: Kevin Kubasik
Component: Testing framework Version: master
Severity: Keywords:
Cc: Triage Stage: Accepted
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no


Invalid restructured text in the documentation should be caught by the test suite and reported as errors. This would hopefully reduce the number of reST error tickets that seem to crop up pretty often.

Change History (5)

comment:1 Changed 11 years ago by Marc Fargas

Triage Stage: UnreviewedAccepted

Given that docs are being refactored I'm not sure if that should be 1.0 or post-1.0 unless such a test is fast to setup.
Note that it would also require docutils to be available on the buildbots.

But surely some kind of testing of docs/ should be done :)

comment:2 Changed 10 years ago by Kevin Kubasik

Owner: changed from nobody to Kevin Kubasik

comment:3 Changed 8 years ago by Eric Holscher

milestone: 1.3
Triage Stage: AcceptedDesign decision needed

This seems like something that might work better as a Sphinx plugin. I know that sphinx will alert us if our documentation is broken or missing, so it seems like this might be invalid these days.

Going to make this 1.3 and a DDN, though I think it should be wontfix'd.

comment:4 Changed 8 years ago by Russell Keith-Magee

Resolution: wontfix
Status: newclosed
Triage Stage: Design decision neededAccepted

I agree with Eric. A "make html" build already reports errors, so we already have a way of detecting "failures" -- we just need to run it.

On top of that, a clean "make html" build takes quite a while. This means it isn't ideal for a unittest, which generally relies of having lots of tests that are quick to run.

If we're going to do this, it really should be done as a step in a buildbot/CI build system, not as a test in the test suite.

comment:5 Changed 7 years ago by Jacob

milestone: 1.3

Milestone 1.3 deleted

Note: See TracTickets for help on using tickets.
Back to Top