-
Notifications
You must be signed in to change notification settings - Fork 1
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
Client developer may use packaged fixtures when integrating Compensated #68
Comments
@jalcine - nice! I've updated the issue body to add some acceptance criteria and sprout a feature definition. I think this is a pretty big chunk of work (likely exceeding our "4 hour timebox") so I've added the epic label. As a thank you for taking the time to put this issue together, I've transferred you 20 points from my personal patronage account balance. These points are worthless for now, but may be redeemed for a share of the profits generated by Zinc (you know, once we have them :)). |
One of the big challenges for working with using compensated is a lack of clarity on what the actual data structure coming out will look like. This gives client developers a tool to programmatically verify their implementation by firing raw events from payment processors through their compensated implementation. See: #68
@jalcine - Do you think this is kind of where you want this to be headed: #72 The goal here is to make it possible for you to generate events from any of the payment processors we support and throw them at a compensated-proxy or a ruby project that is using the compensated gem so you can programmatically test scenarios without having to assemble the fixtures yourself. Thoughts? |
This satisfies the needs I'll have when wanting to incorporate Compensated! |
* 🌱🎉Sprout compensated-spec project for fixtures One of the big challenges for working with using compensated is a lack of clarity on what the actual data structure coming out will look like. This gives client developers a tool to programmatically verify their implementation by firing raw events from payment processors through their compensated implementation. See: #68
Currently, the core
compensated
library holds a lot of useful code around the fixtures for testing responses from Stripe and Apple Pay. Moving them into a separate library (ideallycompensated-spec
) will allow any other Compensated gem to use them and share changes upstream. This can be also be used by other projects that want to test how Compensated responds to particular events.Feature Definition
This Issue May Be Closed When
compensated-spec
module that is packaged as it's own gem.compensated-spec
to test their integration.compensated-ruby
usescompensated-spec
for all its fixturesspec/stripe
- Usecompensated-spec
fixtures to testcompensated-ruby
andcompensated-proxy
#83spec/apple_iap
-compensated-spec
supports testing Apple In-App purchase events #84spec/gumroad
compensated-proxy
usescompensated-spec
for all its fixtures - Usecompensated-spec
fixtures to testcompensated-ruby
andcompensated-proxy
#83compensated-rails
usescompensated-spec
for all its fixturesCHANGELOG.md
to indicate this new feature.compensated-spec
and published it atwww.zinc.coop/compensated/testing-your-integration
The text was updated successfully, but these errors were encountered: