Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Arti Arti
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 140
    • Issues 140
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 9
    • Merge requests 9
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Core
  • ArtiArti
  • Issues
  • #52
Closed
Open
Created Dec 18, 2020 by Lunar@lunarContributor

Add a test framework for the path selection algorithm

DirPathBuilder.pick_path and ExitPathBuilder.pick_path currently lack tests. Ideally, we would want to add some way to test these methods against various network topology and check the selected paths.

What I thought of, so far:

  • mock DirInfo and most of the objects it references,
  • create a consensus document from a human readable description of the network and then parse it into a DirInfo,
  • instantiate a full DirInfo using code to help us do that.

The testing category on crates.io is worth investigating.

Anyway, this issue is mostly for collecting ideas for now, so if you have any, or even a suggestion of what should be done exactly, let's hear it. :)

Assignee
Assign to
Time tracking