Partnered Account for Testing Purposes

[Dist]

@DarkSwordsman

I think that’s a terrible excuse. Why should the user have to reconstruct the Twitch API and keep it up to date with the existing API?

You don’t have to “reconstruct the Twitch API”, you can literally copy/paste examples from the docs to use as mock data.

@DarkSwordsman

Also, what happens if a user has local or automated github tests that will pass with their test cases, but because the API had an update, it fails in production? It’s maybe fine if you’re doing a quick test locally, but it doesn’t work in faster or more long-term environments.

Twitch announce breaking changes to documented services well in advance, so there should be sufficient time to make any required adjustments to testing as needed. The vast majority of developers (ranging from new developers to larger organisations) have handled the rare occasions where there has been a breaking change to the API without issue.

@DarkSwordsman

There’s no excuse for Twitch to not have a sandbox for their API. They are one of the largest companies on earth and hundreds of smaller companies can do it, so why can’t they?

Amazon may be one of the largest companies on Earth, but Twitch certainly isn’t, Creating what you’re suggesting isn’t some simple thing they can throw out there, it takes development time away from other features, and requires time and effort to maintain. Twitch may be working on such features already for all we know as this is nothing new what you’re suggesting, but just keep in mind this is far from essential or critical as the majority of developers have integrated with the Twitch API fine for years, and so would be prioritised as such when it comes to where they choose to focus their resources.