You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
End-to-end test the replication/recovery process #390
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).
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).
Activity
meejah commentedon 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).