The existing tests are generally pretty powerful but have relatively few static vectors, and mostly depend on lots of cycles to get good coverage. For deployment, it would be good to have a acceptably compact (maybe even small enough to just go in the production lib and run as part of _start()) vectors that achieve relative (as much as tests can) completeness on every use.
Locally I have an enormous collection of random (from various strategies) and white-box constructed vectors from many cpu months, about 30 gigabytes worth since I started saving ’effective’ ones which so far have mostly just been used to check agreement with OpenSSL. I’m currently measuring branch/condition hits for each of them in each of our compile configurations, and then I plan on running a set-cover solver to reduce them to a (hopefully!) small set.