[benjaminwil]

Summary

I am currently working on the payment method configuration views for the new solidus_admin gem. I have found it valuable to have access to a test payment method that has uses all of the supported preference types that Solidus currently supports as I build out form components.

I can think of a few reasons this would be valuable to other developers:

1. The bogus credit card method now provides better documentation for what payment methods can do out-of-the-box. This is advantageous to developers, but also to any admin user evaluating Solidus.
2. It allows us to write browser integration tests for payment methods that actually use preferences. In the real world, most payment methods utilize preferences. But until now, our test payment methods didn't really.
3. Like I implied earlier: anyone debugging or developing features in solidus_admin could benefit from a muscular test payment method.

Checklist

Check out our PR guidelines for more details.

The following are mandatory for all PRs:

• I agree that my PR will be published under the same license as Solidus.
• I have written a thorough PR description.
• I have kept my commits small and atomic.
• I have localized any and all user-facing strings that I added to the source code.
• I have used clear, explanatory commit messages.

The following are not always needed:

• 📖 I have updated the README to account for my changes.
• 📑 I have documented new code with YARD.
• 🛣️ I have opened a PR to update the guides.
• ✅ I have added automated tests to cover my changes.
• 📸 I have attached screenshots to demo visual changes.

[jarednorman]

I like this.