Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
exarkun opened this issue May 20, 2022 · 1 comment
Open

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

exarkun opened this issue May 20, 2022 · 1 comment

Comments

@exarkun
Copy link
Collaborator

exarkun commented May 20, 2022

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).

@meejah
Copy link
Collaborator

meejah commented May 21, 2022

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
Labels
None yet
Development

No branches or pull requests

2 participants