Skip to content

End-to-end test the replication/recovery process #390

Open

Description

@exarkun

Replication/recovery requires a lot of pieces to work nicely together. The unit tests do alright but they don't show that the system works when all of the units are combined. More than that, they're a really inconvenient place to put any tests for interactions between different versions of the software (and the resulting state).

Add a different kind of tests that shows replicas are really usable for recovery and that a replica created by one version of the software can be recovered using other versions of the software (presumably, usually, newer versions).

Activity

  1. meejah commented on May 21, 2022

    @meejah
    Collaborator

    It might be better to have versions of the software too then, especially if a "different repo" will contain these tests (maybe Gridsync makes sense? I believe it already has "higher level" tests like this).
    If nothing else, using tags would help the humans looking at things (instead of parsing a SHA hash from JSON).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions