Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
rdsys
rdsys
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 16
    • Issues 16
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Package Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • The Tor Project
  • Anti-censorship
  • rdsysrdsys
  • Issues
  • #6

Closed
Open
Opened Sep 04, 2020 by Philipp Winter@phwMaintainer

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
Sponsor 30 - Objective 2.3
Milestone
Sponsor 30 - Objective 2.3
Assign milestone
Time tracking
None
Due date
None
Reference: tpo/anti-censorship/rdsys#6