Ticket #9837 (closed: fixed)

Opened 6 years ago

Last modified 5 years ago

Sphinx systemtest

Reported by: Andrei Savici Owned by: Andrei Savici
Priority: major Milestone: Release 3.3
Component: Documentation Keywords:
Cc: petersonpf@… Blocked By:
Blocking: Tester: Peter Peterson

Description

Since some of the warnings appear in the summary or init functions in algorithms, it is not easy to spot them. There should be a systemtest to check for the most common mistakes

Change History

comment:1 Changed 6 years ago by Andrei Savici

  • Status changed from new to assigned

comment:2 Changed 6 years ago by Andrei Savici

  • Milestone changed from Backlog to Release 3.3

comment:3 Changed 6 years ago by Andrei Savici

  • Status changed from assigned to inprogress

Systemtest for sphinx warnings. Refs #9837

Changeset: 5ddf8b21f3b117862f48113303e638eb0aa6d87a

comment:4 Changed 6 years ago by Andrei Savici

  • Status changed from inprogress to verify
  • Resolution set to fixed

Testing of feature/9837_sphinxwarnings in systemtests

  1. SystemTests should pass
  2. Change category (easier for python algorithms) to something nonexistent, i.e. xPythonAlgorithms
  3. Add a " *something " in some property, or in summary
  4. Add " |Q| " somewhere in summary or properties
  5. Add " Python <http://www.python.org/>_ " somewhere in properties

You should get errors for 2-5. Note that the rst file is NOT tested, but those warnings show up more explicitly in the builds log

comment:5 Changed 6 years ago by Peter Peterson

  • Status changed from verify to verifying
  • Tester set to Peter Peterson

comment:6 Changed 6 years ago by Pete Peterson

  • Status changed from verifying to closed

Merge remote-tracking branch 'origin/feature/9837_sphinxwarnings'

Full changeset: ​a292f8968c13b91024db1b179321c5c46c0a97d8

comment:7 Changed 5 years ago by Stuart Campbell

This ticket has been transferred to github issue ​10679

Note: See TracTickets for help on using tickets.