Test secret/publishable keys get overwritten with live keys on payment processor configuration save

When I go to configure my Stripe payment processor (https://site/civicrm/admin/paymentProcessor), the form has fields for:

Live Secret Key
Live Publishable Key
Test Secret Key
Test Publishable Key
I input the values provided by the Stripe dashboard under my account settings. All four values are different, and the keys clearly identify whether they are for test or live, so I know I'm putting right values in the right fields.

When I hit save, the test secret key gets overwritten by the live secret key, and the test publishable key gets overwritten by the live publishable key. No matter how many times I go in to edit the payment processor configuration, re-enter the correct test values, and re-save, the next time I edit the payment processor the test values are overwritten by the live values.

I have also tried creating a totally brand new payment processor configuration – same result.

The net result is that I cannot run test transactions because Stripe sees me using a live key for a test customer.

I reported the issue to the stripe extension developer ([here] | https://github.com/drastik/com.drastikbydesign.stripe/issues/133) and another user reported that he was having the same issue with the paypal payment extension. Thus we believe this is an issue with CiviCRM and not with the extension itself.