Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • rdsys rdsys
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 56
    • Issues 56
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 2
    • Merge requests 2
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and 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
  • Anti-censorship
  • rdsysrdsys
  • Issues
  • #6
Closed
Open
Issue created Sep 04, 2020 by Philipp Winter@phw

Implement integration tests

Let's figure out a way to implement integration tests for rdsys. Here's a simple suggestion for a simple shell script:

  1. Write a simple cached-extrainfo file to disk.
  2. Start the backend.
  3. Start the HTTPS distributor.
  4. Use curl to fetch bridges from the HTTPS distributor.
  5. Make sure that the bridges are the same as those in the cached-extrainfo file.

There are probably smarter ways to accomplish this. Let's make sure that our integration tests are lightweight and can be run as part of a continuous integration test infrastructure.

Assignee
Assign to
Time tracking