-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Seems to hide insecure certificate exceptions/helpful errors? #3
Comments
No, but what does the |
It stops supertest from checking the validity of the certificates so we you are using self-signed for local dev or hitting environments with otherwise non-legit certificates (like test environments). Without it supertest throws errors like |
Ok, so the issue is that those errors aren't reported correctly, like the assertion error you mentioned? Can you post a stack trace? |
|
When testing internal APIs with insecure/untrusted certificates I was getting error
when running a test similar to
until I thought to try using the .disableTLSCerts() option (the API under test int his scenario does not use a securely-signed certificate)
Unless I'm mistaken I recall SuperTest providing an error in these scenarios that would more easily let the user realize it didn't connect because of an insecure certificate. Is the plugin hiding the exception?
The text was updated successfully, but these errors were encountered: