Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • S sbws
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 6
    • Issues 6
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • 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
  • Network Health
  • sbws
  • Issues
  • #28933
Closed
Open
Issue created Dec 22, 2018 by juga@jugaMaintainer

Run one sbws main loop using the test network as part of integration tests

Currently is not possible to run the main sbws scanner function run_speedtest because it uses threads, which doesn't work with pytest. The threads could be mocked or run one single process, but behaviour would be different as with threads. Since integration tests launch a testing network, it's possible to just run sbws configured to run that network. It's also possible to make sbws stops after the first loop when being in a testing network so that it doesn't run forever. While this won't behave the same way as in a public network, it might still help to find bugs.

Assignee
Assign to
Time tracking