Okay, we’ve finally figured out what was going on.
Auth Error) We traced the mocha connection and found it was trying to create its own DB with “-mocha” appended. Our cloud broker doesn’t allow a DB to be created on the fly, so instead we’ve provisioned a DB with name “appDBname-mocha” and configured Velocity’s connection string for just “appDBname”.
404 handshake errors) Turns out Velocity was respecting our proxy settings and attempting to leave our intranet, which caused this issue. Disabling our proxy settings prior to running the test suite fixes the issue.