Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • dumux dumux
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 100
    • Issues 100
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 92
    • Merge requests 92
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • dumux-repositoriesdumux-repositories
  • dumuxdumux
  • Issues
  • #887
Closed
Open
Issue created May 20, 2020 by Timo Koch@timokOwner

[doxygen] Exclude tests from doxygen?

There is a number of arguments for simply removing the tests and all files in the test directory from doxygen

  • The is a large amount of classes and files that distract from the actual classes and files in the Dumux core

  • The code doc of the tests is poorly structured and doesn't help much

  • Unclear which information gain we get from inclusion

  • Our doxygen takes very long to compile and is quite large. This would help reducing it a bit (all dumux source files in the dumux folder are 231,172 lines total, all source files (.hh,.cc) in the test folder are 90,691 lines total; using find . -name '*.hh' -o -name '*.cc' | xargs wc -l)

  • Much of the doc is not very good (while that is a problem in itself and the doc comments in the tests should actually be of high quality too, this is in the current stage really distracting). Even if it would be better the other points remain.

I navigated through the test docs in the online class documentation a bit. I didn't find anything useful in the Test & Benchmarks section. Any other opinions and arguments for keeping it?

Edited May 20, 2020 by Timo Koch
Assignee
Assign to
Time tracking