Stripe is putting out console warnings in tests

[begedin]

Problem

A bunch of our tests, when executed, output a console.warn into the terminal, with

You may test your Stripe.js integration over HTTP. However, live Stripe.js integrations must use HTTPS.

This pollutes the test output, which

• makes it more difficult to see which test failed when executing ember-exam
• makes it more difficult to see why and which tests failed on circle
• implies our tests may be contacting the stripe API, which possibly should not have to happen

We should

• identify where the warning is being called
• figure out if it's due to contacting the stripe API
• figure out how to either avoid, or, if not possible, squelch it

[begedin]

Note that the closing of this issue may involve submitting and closing an issue on an external addon, for example, ember-stripe-service, or ember-stripe-elements. Further investigation will reveal this.

[joshsmith]

This is part of Stripe.js (served from Stripe) and occurs when we actually call out to Stripe in places, which in some cases we do actually want to do (as an integration test). They do the console.warn themselves.

It's possible we could silence it with ember test --silent. Barring that, we could also run the ember server with a self-signed SSL cert in CI.