In that regard a non-destructive test is somewhat lacking.
Personally I’ve opted to just write my data and run a scrub / verify occasionally.
I like the smart test idea too though.
I have a few layers of software block antics going on so I like the e2e nature of restic check --read-data and other high level validations, (a ZFS/btrfs scrub is sort of a middle level validation.)
Smart long test only does a full read test, I believe.
you don’t need the non-destructive option on new empty drives. Non-destructive is for drives with data you’d want to keep.
I don’t think it makes sense testing drives 3 at a time. If all drives running overheats you need better cooling, since I assume you’ll use some kind of redundant raid and probably the drives will run at the same time in real use too. See it as a test of your cooling setup..
personally I’ve done a single badblocks test on new drives and then a scrub after filling them. Two full passes with large drives is a lot and takes ages. But if you have the time and motivation why not?