# Sandbox testing environment

**URL:** <https://www.patreondevelopers.com/t/sandbox-testing-environment/145>\
**Category:** Uncategorized\
**Created:** [December 3, 2017, 11:05pm UTC](https://www.patreondevelopers.com/t/sandbox-testing-environment/145 "2017-12-03T23:05:50Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Bilge](https://yyz2.discourse-cdn.com/flex036/user_avatar/www.patreondevelopers.com/bilge/32/89_2.png) [@Bilge](https://www.patreondevelopers.com/u/Bilge)\
**Post date:** [December 3, 2017, 11:05pm UTC](https://www.patreondevelopers.com/t/sandbox-testing-environment/145/1 "2017-12-03T23:05:50Z")

</div>

Is there a testing environment so I can test my theoretical Patreon integration is working? I don’t have any Patreons yet, so it would be difficult, if not impossible, to positively assert any such integration is working correctly without some sort of test environment to work against.

---

<div class="post-metadata">

**Author:** ![tal](https://yyz2.discourse-cdn.com/flex036/user_avatar/www.patreondevelopers.com/tal/32/4_2.png) [@tal](https://www.patreondevelopers.com/u/tal)\
**Post date:** [December 5, 2017, 12:42am UTC](https://www.patreondevelopers.com/t/sandbox-testing-environment/145/2 "2017-12-05T00:42:00Z")

</div>

Great question. As you can imagine, many developers [understandably] share this pain. On our end it will unfortunately be a bit of an infrastructure journey before we can make a real sandbox happen.

In the short term, the not-ideal answer I can give is to

1. **Use two (or more) accounts and pledge to yourself**
2. **Set the campaign to “per post” so the fake patrons don’t actually get charged**

Not the best answer - take solace in that you’re not the only one with the pains.

> [@API Feature Wishlist](https://www.patreondevelopers.com/t/api-feature-wishlist/93/4):
>
> Developer Sandbox I know you’re already aware of this, but figured I’d write it down anyway. \>\_\< In such a sandbox, it would be great to simulate dates and charging cycles… Waiting 29 days to test out a feature is a little inconvenient. stuck_out_tongue Ability to alter user, campaign data Being able to alter a user’s data. For example, setting their avatar. Along the same lines, being able to alter the description, rewards, goals, etc. Make posts, send messages on the creators behalf Si…

> [@2018 API Planning](https://www.patreondevelopers.com/t/2018-api-planning/113/2):
>
> Please provide a demo Patreon account, with hundreds of Patrons in different tiers and open-to-all read-only credentials and completely static (no new patrons). This way we can write full stack automated tests and be 100% sure the integrations are working, while we change our code.

---

<div class="post-metadata">

**Author:** ![Bilge](https://yyz2.discourse-cdn.com/flex036/user_avatar/www.patreondevelopers.com/bilge/32/89_2.png) [@Bilge](https://www.patreondevelopers.com/u/Bilge)\
**Post date:** [December 5, 2017, 12:57am UTC](https://www.patreondevelopers.com/t/sandbox-testing-environment/145/3 "2017-12-05T00:57:19Z")

</div>

This should do for now so long as:

1. There’s no risk of being charged and losing money.
2. I do not need to complete any forms of verification including any legal documents in order to accept the (fake) pledge(s).

---

<div class="post-metadata">

**Author:** ![tal](https://yyz2.discourse-cdn.com/flex036/user_avatar/www.patreondevelopers.com/tal/32/4_2.png) [@tal](https://www.patreondevelopers.com/u/tal)\
**Post date:** [December 5, 2017, 1:01am UTC](https://www.patreondevelopers.com/t/sandbox-testing-environment/145/4 "2017-12-05T01:01:10Z")

</div>

As long as you don’t post a ‘paid post,’ no charges should take place.