That’s the widespread historical approach to what the Test connection
button does, as seen here:
Feature request: Test write permissions on ‘FTP Test connection’ #2473
Test write permissions on ‘FTP Test connection’ #2500 was PR and said
Maybe we should move it later, so this can be done for all backends.
but there is always more that “could” be done than volunteers to do them.
would probably be the sort of code to change if anybody is willing to do it.
The official interface definition of exactly what a Test
should do is vague:
but if more backends can do a better test, it would save having to point to:
Duplicati.CommandLine.BackendTester.exe and give directions for its use
(generally I advise editing Export As Command-line URL for empty folder).
Before you start using a particular backend to use as a backup target, you can use the Backend Tester to get an indication of the integrity of that backend.
I think this is too long for a quick test, but a better quick test would be nice.
Duplicati only exists and improves thanks to volunteers. More are needed.
There are ample opportunities in code, test, docs, support, planning, etc…