for some of our tests (for example, the ./e2e tests) we have credentials hard-coded. This is not an issue in itself, but leads to confusion and probably isn't a great practice.
track down all of the areas where test credentials (such as private keys) are hard-coded and update them to be generated instead
for some of our tests (for example, the
./e2etests) we have credentials hard-coded. This is not an issue in itself, but leads to confusion and probably isn't a great practice.track down all of the areas where test credentials (such as private keys) are hard-coded and update them to be generated instead